Below is a silly toy service that I've used to prove out some of the s6 behavior.
$ cat date/run #!/bin/bash exec date > now.date $ s6-supervise date & [5] 3916351 $ cat date/now.date Tue Sep 8 13:32:21 PDT 2015 $ s6-svstat date/ down (exitcode 0) 0 seconds, normally up, want up, ready 0 seconds $ cat date/now.date Tue Sep 8 13:32:23 PDT 2015 $ s6-svstat date/ down (exitcode 0) 0 seconds, normally up, want up, ready 0 seconds $ cat date/now.date Tue Sep 8 13:32:24 PDT 2015 $ s6-svstat date/ down (exitcode 0) 0 seconds, normally up, want up, ready 0 seconds That's all fine and sensical. $ s6-svc -dx date/ [5] Done s6-supervise date $ s6-svc -dx date/ s6-svc: fatal: unable to control date/: supervisor not listening $ s6-svstat date/ down (exitcode 0) 6 seconds, normally up, want up, ready 6 seconds $ cat date/now.date Tue Sep 8 13:33:07 PDT 2015 $ s6-svstat date/ down (exitcode 0) 10 seconds, normally up, want up, ready 10 seconds $ cat date/now.date Tue Sep 8 13:33:07 PDT 2015 The "want up" here seems patently false. The last command sent was "-dx", which tells the thing to go down. The "normally up" is fine, since there's no `down` file. Is this a bug or a feature?
