You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am converting some existing services to use supervising daemon.
it is great when i can use only configuration files /etc/conf.d modifications. if i use /etc/init.d modifications, like in doc examples, it can lead to upgrade issues and more.
supervise does not need pid file creation by init.d program, and practically dont need to wait.
so it does not support --wait argument, and throws error:
looking at the examples, i really don't know why start_stop_daemon_args are being used for supervise_daemon at all, as you can see both set args for ssd, those args shouldn't carry over, and that's the bug
i am converting some existing services to use supervising daemon.
it is great when i can use only configuration files /etc/conf.d modifications. if i use /etc/init.d modifications, like in doc examples, it can lead to upgrade issues and more.
example of config modification to use supervise:
but most /etc/init.d scripts use of --wait argument, to wait for pid file.
example:
supervise does not need pid file creation by init.d program, and practically dont need to wait.
so it does not support --wait argument, and throws error:
i think it will be great to supervise-deamon accept --wait argument, without error.
maybe with einfo that wait will be always zero.
tnx
The text was updated successfully, but these errors were encountered: