Bug#727708: init system discussion status

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Cameron Norman writes ("Re: Bug#727708: init system discussion status"):
> On Thu, Jan 2, 2014 at 10:16 AM, Ian Jackson <
> ijackson@chiark.greenend.org.uk> wrote:
...
> | 9. [ Policy should provide non-binding suggestions to Debian
> > |    contributors who are converting daemons to upstart and/or systemd,
> > |    for example:
> > |
> > |    (a) If changes are necessary to the core daemon code, make those
> > |        changes acceptable to the daemon's upstream if possible.
> > |
> > |    (b) It is fine to introduce new code in the main body of the daemon
> > |        to support non-forking startup, socket activation or readiness
> > |        signalling.
> > |
> > |    (c) Support for upstart is usually best provided with the
> > |        raise(SIGSTOP) non-forking daemon readiness protocol, unless
> > |        and until a better protocol is available.
> > |
> 
> Should it not be added that raise(SIGSTOP) should only be used with a
> command line option (like --debian-Z) to ensure that the daemon does not
> hang on sysv or systemd?

I think in practice this isn't going to be much of a problem but I
don't mind putting it in this section of my proposed resolution.  This
is advice to the the policy editors which they can ignore it if they
feel it's clogging up the manual.

Ian.