See this issue.
Docker best practise to Control and configure Docker with systemd.
-
Create
daemon.json
file in/etc/docker
:{"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}
See this issue.
Docker best practise to Control and configure Docker with systemd.
Create daemon.json
file in /etc/docker
:
{"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}
-- show running queries (pre 9.2) | |
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
FROM pg_stat_activity | |
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
ORDER BY query_start desc; | |
-- show running queries (9.2) | |
SELECT pid, age(clock_timestamp(), query_start), usename, query | |
FROM pg_stat_activity | |
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |
The iMX7D reference design has two 512MB of RAM for a total of 1GB (math). With RAM costs on the cheap it is likely that your custom embedded platforms with the iMX7D will also have 1GB of RAM. But what happens when you are trying to cut costs, or just not over engineer and go with a single 512MB.
There are some tutorials online, but I couldn't find one that included all the changes that need to be made. So here I am.
There are some things to know before going further. I was using Das U-boot for my bootloader, and working with a linux kernel new enough to have DTS files (I think that happened in 3.7 for ARM architecture).
We'll start in u-boot and go up from there. The iMX7D DCD (Device Configuration Data) file is located in the board directory as imximage.cfg There are 5 values that need to be changed and they are, the Master Register and Address Map Registers 0/1/5/6. Search the iMX7D Reference Manuel for more information on each of the registers.
-DATA 4 0x307a0000 0x01040001
By: Alastair Tse @liquidx
Updated: 2021-12-05
This is a guide for installing Linux on a Technexion NXP IMX7 board. This is a board that was part of the Android Things Starter Kit (now discontinued).
There are some dead ends in this guide where I got to a point where I failed. I'm documenting this so that it can help anyone else who is trying the same thing.
Before starting, there are a few useful sources of information:
docker logs nginx 2>&1 | grep "127." | |
# ref: http://stackoverflow.com/questions/34724980/finding-a-string-in-docker-logs-of-container |
import * as S from '@effect/schema/Schema' | |
import { Context, Effect } from 'effect' | |
export interface IFetcher { | |
fetch: typeof fetch | |
} | |
export const TFetcher = Context.Tag<IFetcher>('IFetcher') | |
class FreshFetcher implements IFetcher { |
Format String Bugs(以降, FSBとする)とは, sprintf()
やfprintf()
などのprintf関数群やsyslog()
などのFormat Strings(以降, 書式指定子とする)を扱える関数において, ユーザが自由に書式指定子を配置できるバグである. これを利用した攻撃手法をFormat String Attacksと呼び, この攻撃によりターゲットとなるプロセスがアクセス可能な任意のメモリの読み書きが行えるようになる. また, それを利用しプログラムの制御を乗っ取ることも可能である.
実際のプログラムに多く存在するとは到底言えないような脆弱性ではあるが稀に見つかることはある. CVE-2012-0809[1]ではsudoのデバッグ機能にFSBが見つかり, 実際にlocal exploitが公開されたりもした. 前述の通り珍しいものではあるが, 任意のメモリの書き換えができるなど非常に強力なものであることからCTFではよく題材にされる.
この記事ではFSBの検証に以下の環境を使用した.
sh-4.3$ uname -a
Linux Arch_Laptop 4.0.4-1-ARCH #1 SMP PREEMPT Mon May 18 06:43:19 CEST 2015 x86_64 GNU/Linux
// | |
// Lookup Tables for Marching Cubes | |
// | |
// These tables differ from the original paper (Marching Cubes: A High Resolution 3D Surface Construction Algorithm) | |
// | |
// The co-ordinate system has the more convenient properties: | |
// | |
// i = cube index [0, 7] | |
// x = (i & 1) >> 0 | |
// y = (i & 2) >> 1 |
https://www.nseindia.com/corporates/datafiles/AN_NAV_LATEST_ANNOUNCED.csv | |
https://www.nseindia.com/corporates/datafiles/BM_All_Forthcoming.csv | |
https://www.nseindia.com/corporates/datafiles/CA_TODAY_SPLIT.csv | |
https://www.nseindia.com/corporates/datafiles/CA_TODAY_BONUS.csv | |
http://www.nseindia.com/corporates/datafiles/CA_LAST_1_MONTH_BONUS.csv | |
https://www.nseindia.com/corporates/datafiles/CA_LAST_1_WEEK_SPLIT.csv | |
https://www.nseindia.com/corporates/datafiles/CA_LAST_1_WEEK_BONUS.csv | |
https://www.nseindia.com/corporates/datafiles/CA_MORE_THAN_24_MONTHS_SPLIT.csv | |
https://www.nseindia.com/corporates/datafiles/CA_MORE_THAN_24_MONTHS_BONUS.csv | |
http://www.nseindia.com/corporates/datafiles/CA_LAST_1_MONTH_RIGHTS.csv |
These are sample scripts in Python and Node.js for controlling the output format of the Gemini API using JSON schemas.
In a previous report, "Taming the Wild Output: Effective Control of Gemini API Response Formats with response_mime_type," I presented sample scripts created with Google Apps Script. Ref Following its publication, I received requests for sample scripts using Python and Node.js. This report addresses those requests by providing sample scripts in both languages.