From 49f1f9efe1874449303ca8c95a35a7b2bd4e13a0 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 25 Jun 2015 19:17:43 +0000 Subject: - doc fixes (changed mentions of s6-notifywhenup) - s6-svc -X - rc for 2.1.6.0 --- doc/s6-svc.html | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) (limited to 'doc/s6-svc.html') diff --git a/doc/s6-svc.html b/doc/s6-svc.html index 5d45972..2de8ba4 100644 --- a/doc/s6-svc.html +++ b/doc/s6-svc.html @@ -60,6 +60,13 @@ Automatically restart it when it dies.
  • -x : exit. When the service is asked to be down and the supervised process dies, s6-supervise will exit too. This command should normally never be used on a working system.
    • +
  • -X : close fds and exit. Like -x, but +s6-supervise will immediately close its +stdin, stdout and stderr. This is useful when s6-supervise has descriptors +open to the service it is supervising and the service is waiting for them +to close before exiting. Note that if this option is used, the last +execution of the service's finish script will be run with +stdin, stdout and stderr redirected to /dev/null.
  • -O : Once at most. Do not restart the supervised process when it dies. If it is down when the command is received, do not even start it.
    • @@ -71,9 +78,10 @@ timeout is 0, which means that s6-svc will block indefinitely.
  • -D : s6-svc will not exit until the service is down.
  • -U : s6-svc will not exit until the service is up and ready as notified by the daemon itself. -Be careful to only use this command on services that send readiness -notifications and are managed by s6-notifywhenup, -else the command will never be successful.
    • +If the service directory does not contain +a notification-fd file to tell +s6-supervise to accept readiness +notification, s6-svc will print a warning and ignore the command.

    Usage examples

    -- cgit v1.2.3