Bug#727708: init system discussion status
Tollef Fog Heen <tfheen@err.no> writes:
> ]] Ian Jackson
>> 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 see why you think that doing so because a configuration file
> tells it to, is wrong.
> I think it's a bad thing to overspecify how a daemon is configured,
> which I think you're doing here.
I basically agree with the latter point, but the reason why I wouldn't
want to use a configuration file is that administrators are still going to
want to start daemons by hand (such as when debugging things), presumably
with the same configuration as when the daemon is run by the init system.
The SIGSTOP behavior is rather confusing when you're not expecting it.
That's why I prefer either environment variables (which are the easiest to
keep clear of the administrator action, but which have the problem of
leaking) or a command-line option (which the administrator has to remember
to remove when starting things by hand, but which don't leak).
I think it's important that anything we say here is marked as technical
advice, as Ian helpfully distinguished in the draft proposal, which means
that the TC is not *requiring* things and maintainers can go a different
direction if the advice doesn't make sense. That makes it less of a
specification and more of a collection of things we think make sense and
that one should probably follow unless one has thought about the problem.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: