Re: is it OK for invoke-rc.d stop not to stop?
Henrique de Moraes Holschuh writes:
> /etc/init.d/anything stop MUST stop the service at all costs, even if it
> has to kill -9 the daemon.
True of /etc/init.d/anything but not of invoke-rc.d. From the man page:
INIT SCRIPT POLICY
invoke-rc.d introduces the concept of a policy layer which is used
to verify if an init script should be run or not, or if something
else should be done instead. This layer has various uses, the most
immediate ones being avoiding that package upgrades start daemons
out-of-runlevel, and that a package starts or stops daemons while
inside a chroot jail.
The policy layer has the following abilities: deny or approve the
execution of an action; request that another action (called a
fallback) is to be taken, instead of the action requested in
invoke-rc.d's command line; or request multiple actions to be
tried in order, until one of them succeeds (a multiple fallback).
> BTW, anyone using start-stop-daemon -exec for *stop* fix your scripts
I count sixteen such scripts on this system. Fix /etc/init.d/skeleton and
firstname.lastname@example.org (John Hasler)
Dancing Horse Hill