Bug#727708: upstart proposed policy in Debian [and 1 more messages]
Uoti Urpala <uoti.urpala@pp1.inet.fi> writes:
> BTW it's worth noting that in the typical daemon case where "readiness"
> means the listening socket is ready to accept requests, the right way to
> convert the daemon to a new API is to use socket activation, which
> removes the need for separate start-up completion notification. Thus the
> need to use sd_notify() for this purpose should be the exception rather
> than the rule. This means that daemons which would use libsystemd-daemon
> for startup notification and nothing else (and would thus be potential
> candidates to abuse SIGSTOP) should be rare.
Good point. Anything that's using socket activation probably doesn't
really need additional synchronization.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: