From 90b12bd71bb9fc79a4640b9112c13ef529d0196a Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Fri, 5 Dec 2014 22:26:11 +0000 Subject: Initial commit --- doc/s6-fghack.html | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 doc/s6-fghack.html (limited to 'doc/s6-fghack.html') diff --git a/doc/s6-fghack.html b/doc/s6-fghack.html new file mode 100644 index 0000000..ba3f351 --- /dev/null +++ b/doc/s6-fghack.html @@ -0,0 +1,50 @@ + + + + + s6: the s6-fghack program + + + + + + +

+s6
+Software
+skarnet.org +

+ +

The s6-fghack program

+ +

+s6-fghack is an anti-backgrounding tool. +

+ +

Interface

+ +

+     s6-fghack prog...
+

+ +

s6-fghack opens a lot of file descriptors (all writing to a single pipe).
Then it forks and executes prog....
If something gets written on one of those descriptors, it's a bug in prog. +s6-fghack then complains and exits 102.
Unless prog... goes out of its way to close descriptors it does know about, +s6-fghack is able to detect when prog... exits. It exits with the same exit +code (or 111 if prog... has crashed).

+ +

Notes

+ +

+ s6-fghack is what it says: a hack. Ideally, you should never have to use it. +It is only useful when you want to supervise a daemon that does not provide a +"stay in the foreground" option; and even then, the right thing is to report +this as a bug to the daemon author and have it fixed. +

+ + + -- cgit v1.3.1