Bug#491318: init scripts "should" support start/stop/restart/force-reload - why not "must"?
Lars Wirzenius <liw@liw.fi> writes:
> pe, 2008-07-18 kello 09:51 -0700, Russ Allbery kirjoitti:
>> Peter Samuelson <peter@p12n.org> writes:
>>> The `start', `stop', `restart', and `force-reload' options should be
>>> supported by all scripts in `/etc/init.d', the `reload' option is
>>> optional.
>>> Is there any reason not to upgrade "should" to "must"? What is the
>>> point of an init script that does not support those arguments?
>> /etc/init.d/umountfs is an example.
> That script errors out when called with restart, reload, or
> force-reload. Would it be accepable to change them into no-ops instead?
I think that would be acceptable, but more directly to the point, I think
it's also acceptable for it to do what it does now. Changing the Policy
to a must would mean that it would be *required* to change them into
no-ops, and I'm not sure that's justified.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: