Bug#727708: init system discussion status

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

Russ Allbery writes ("Bug#727708: init system discussion status"):
> Cameron Norman <camerontnorman@gmail.com> writes:
> > 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?
> 
> No, because see Colin's point that Debian developers may be doing the
> integration and adding a new command-line option may conflict with
> upstream's intentions or just be more intrusive.  Another reasonable
> option is to use an environment variable that you then unset after
> noticing its existence.  There may be others.  I think it's best to be
> agnostic in the TC decision on how this integration is done, since I think
> it's really a matter of technical detail and won't be controversial, and
> be more verbose about the options in Policy.

I think it would be reasonable to state that the raise(SIGSTOP)
integration should be done with a new command line option OR a new
environment variable; ie that the daemon should not be changed to
raise(SIGSTOP) by default.

I don't know whether it's valuable to mention this explicitly.

If there is any significant risk that anyone might patch a daemon to
SIGSTOP by default then I would want to put something in the
resolution or in policy to suggest not to do that!  Would anyone
really be so daft ?

Ian.