Bug#727708: loose ends for init system decision
On Tue, Dec 31, 2013 at 10:18:08PM -0800, Russ Allbery wrote:
> For upstart readiness, obviously one needs some sort of explicit flag or
> trigger to enable the raise(SIGSTOP) behavior, since that will otherwise
> cause rather obvious problems in getting the daemon to work outside of
> upstart. I prefer to use a command-line flag for this (-Z, per your
> recommendation) since it has to be explicitly enabled and there isn't the
> same sort of safe fallback if it's missing the way that there is for the
> systemd protocol. I don't see any real problem with using an environment
> variable, though, as long as it's unset afterwards so that it's not
> inherited by children.
Bear in mind that this may often be being done by the Debian maintainer
in advance of upstream, and adding a one-character command-line option
is problematic since that stands a decent chance of clashing.
--
Colin Watson [cjwatson@debian.org]
Reply to: