From a3cdeecf0033919e3b5a79c17c19b5ac98719256 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 20 Jul 2015 20:20:54 +0000 Subject: - Add timeout-finish support and "down-readiness" - LOTS of refactoring to make this work - Remove s6-notifywhenup - s6-supervise now rocks the casbah - rc for 2.2.0.0 --- doc/s6-sudod.html | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'doc/s6-sudod.html') diff --git a/doc/s6-sudod.html b/doc/s6-sudod.html index 2c613da..54e9574 100644 --- a/doc/s6-sudod.html +++ b/doc/s6-sudod.html @@ -91,8 +91,8 @@ will set up a privileged program: 
 #!/command/execlineb -P
 fdmove -c 2 1
+fdmove 1 3
 s6-envuidgid serveruser
-s6-notifywhenup -f
 s6-ipcserver -U -1 -- serversocket
 s6-ipcserver-access -v2 -l0 -i rules --
 exec -c
@@ -106,12 +106,15 @@ sargv
 executes the script. 
  
  •  fdmove makes
 sure the script's error messages are sent to the service's logger. 
    • 
+ 
  •  fdmove
+redirects the script's stdout to file descriptor 3. This is useful if
+the service directory contains a notification-fd file containing
+3, so the daemon can perform
+readiness notification by writing a
+newline to its stdout. (The
+-1 option to s6-ipcserver tells it to do this.) 
    • 
  
  •  s6-envuidgid
 sets the UID, GID and GIDLIST environment variables for s6-ipcserver to interpret. 
    • 
- 
  •  s6-notifywhenup primes the
-service for readiness notification (and the
--1 option to s6-ipcserver tells the daemon to actually
-notify when it's ready). 
    • 
  
  •  s6-ipcserver binds to serversocket,
 drops its privileges to those of serveruser, and announces its
 readiness. Then, for every client connecting to serversocket:
-- 
cgit v1.2.3