{"action":"created","issue":{"url":"https://api.github.com/repos/just-containers/s6-overlay/issues/107","labels_url":"https://api.github.com/repos/just-containers/s6-overlay/issues/107/labels{/name}","comments_url":"https://api.github.com/repos/just-containers/s6-overlay/issues/107/comments","events_url":"https://api.github.com/repos/just-containers/s6-overlay/issues/107/events","html_url":"https://github.com/just-containers/s6-overlay/issues/107","id":118278985,"number":107,"title":"Few issues / questions","user":{"login":"robbertkl","id":5704510,"avatar_url":"https://avatars.githubusercontent.com/u/5704510?v=3","gravatar_id":"","url":"https://api.github.com/users/robbertkl","html_url":"https://github.com/robbertkl","followers_url":"https://api.github.com/users/robbertkl/followers","following_url":"https://api.github.com/users/robbertkl/following{/other_user}","gists_url":"https://api.github.com/users/robbertkl/gists{/gist_id}","starred_url":"https://api.github.com/users/robbertkl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robbertkl/subscriptions","organizations_url":"https://api.github.com/users/robbertkl/orgs","repos_url":"https://api.github.com/users/robbertkl/repos","events_url":"https://api.github.com/users/robbertkl/events{/privacy}","received_events_url":"https://api.github.com/users/robbertkl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-22T18:20:08Z","updated_at":"2015-11-23T14:30:48Z","closed_at":null,"body":"Hi,\r\n\r\nJust started using s6-overlay (coming from supervisord) and love it so far. I do have a few issues / questions. Please let me know if I should submit separate issues.\r\n\r\n1. On [this line of init-stage3](https://github.com/just-containers/s6-overlay/blob/a0d61a94fe1126348efb6396175bac63b2644f96/builder/overlay-rootfs/etc/s6/init/init-stage3#L48), `s6-nuke` is called with both `-t` and `-h`. This causes both `HUP` and `TERM` to be sent to all processes, even though the informative log message mentions only `TERM`. Shouldn't this be `-t` only? The `HUP` causes my process to reload their config, just before getting killed anyway. If there is valid reason for this (which I'd love to learn), I would suggest changing the log message.\r\n\r\n2. Also in [init-stage3](https://github.com/just-containers/s6-overlay/blob/a0d61a94fe1126348efb6396175bac63b2644f96/builder/overlay-rootfs/etc/s6/init/init-stage3#L54), this stage is sleeping (by default) for 5 seconds, before sending `KILL`. It seems to do this every time, even if there are no more processes to \"nuke\". Even if I have a container running services that terminate quickly, `docker stop` (or restarts) will still take 5 seconds, which seems unnecessary. Any ideas / solutions for this?\r\n\r\n3. This might be more of an issue with s6-svscan instead of s6-overlay. With supervisord (running as pid 1), sending a `HUP` to it (or `docker kill -s HUP`), would cause the `HUP` to be \"forwarded\" to all running services. This in turn would make all services reload their configs, as is a common convention for many daemons. With s6-overlay, this does not happen, instead causing the container to (cleanly) exit. Is there a way to forward signals like supervisord does? Might be useful for other signals as well, like `USR1` or `USR2`. Perhaps this is possible using `s6-svscan -s`, but if I understand the documentation correctly, this means we have to handle (i.e. properly deal with) all 6 signals in `.s6-svscan/` scripts, or else signals we be ignored. Any suggestions?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/just-containers/s6-overlay/issues/comments/158951221","html_url":"https://github.com/just-containers/s6-overlay/issues/107#issuecomment-158951221","issue_url":"https://api.github.com/repos/just-containers/s6-overlay/issues/107","id":158951221,"user":{"login":"jprjr","id":4265148,"avatar_url":"https://avatars.githubusercontent.com/u/4265148?v=3","gravatar_id":"","url":"https://api.github.com/users/jprjr","html_url":"https://github.com/jprjr","followers_url":"https://api.github.com/users/jprjr/followers","following_url":"https://api.github.com/users/jprjr/following{/other_user}","gists_url":"https://api.github.com/users/jprjr/gists{/gist_id}","starred_url":"https://api.github.com/users/jprjr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jprjr/subscriptions","organizations_url":"https://api.github.com/users/jprjr/orgs","repos_url":"https://api.github.com/users/jprjr/repos","events_url":"https://api.github.com/users/jprjr/events{/privacy}","received_events_url":"https://api.github.com/users/jprjr/received_events","type":"User","site_admin":false},"created_at":"2015-11-23T14:30:48Z","updated_at":"2015-11-23T14:30:48Z","body":"@glerchundi I think the `HUP` is because the `logutil-service` runs `s6-log` with the `-p` switch, so `s6-log` only exits on a `HUP`, not on a `TERM` https://github.com/just-containers/s6-overlay/blob/master/builder/overlay-rootfs/usr/bin/logutil-service-main#L11\r\n\r\nI think on a usual install or VM you'd want that \"don't exit on `TERM`\" behavior, but I'm wondering if we're OK just letting it exit on a `TERM` in our project. I'm not sure though."}}