Hi! On Sun, 2026-01-04 at 20:45:50 +0000, Andrew Bower wrote: > Package: dpkg > Version: 1.23.3 > Severity: wishlist
> If you specify --notify-await thinking that it will enact the systemd > readiness protocol on a daemon you will be disappointed unless you > also specified --background. > > It would be nice if the notify socket was created, passed on and used > in all cases where --notify-await was specified, not just when > start-stop-daemon is also doing the daemonisation. I would rather not > degrade to using --background when a daemon can already self-daemonise > satisfactorily in order to use this option. I don't see how s-s-d could do that when it's not under --background, because then it cedes control over the executed daemon, and that will not know what to do with the passed notify socket. > The man page does not make it clear that this is the situation and I am > sure I have already deployed this option somewhere uselessly having not > checked the failure case to make sure it was actually effective, so that > aspect is not so much 'wishlist'! Right, I've added consistency checks for the ineffective option combinations (--notify-timeout w/o --notify-await and --notify-await w/o --background), where it will error out. I'll also try to improve the documentation to make this more explicit. Will be part of my next push targeting the next dpkg release. Thanks, Guillem
