Russ Allbery writes ("Bug#727708: upstart proposed policy in Debian [and 1 more messages]"): > I'd like to see both of them support systemd's method, since it's > extensible and provides more general functionality. I think the benefit > of support for SIGSTOP is marginal; adding sd_notify calls is not that > much harder and doesn't have the conceptual weirdness of stopping the > daemon to notify the init system that it's running.
I strongly disagreee. As the upstream author of a daemon I'm - not willing to add a library dependency for this - not willing to write a 50-100 lines of tiresome socket code for this - not willing to copy the library file into my source tree so the result is that userv upstream won't support systemd's readiness protocol. Luckily the systemd socket activation is less fiddly than the general readiness protcol, so for systemd I am doing that instead. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org