Bug#727708: upstart proposed policy in Debian [and 1 more messages]
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Russ Allbery writes:
>> 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.
Yes, we completely disagree.
Among other things, that's about the smallest and least-impactful library
dependency I can imagine. My intent in integrating support for sd_notify
is to just stub out the call when not built with systemd support, which is
pretty trivial to do with Autoconf and means that those who want systemd
integration get it and those who don't care can easily ignore it.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: