Well, it is OK that a script called with reload fails if the service is
not running, but the point is: why ask a reload to a service that is not
running (because disabled), maybe failing even a pre/post install script?
Because reload (and force-reload, if it was a sane thing which it isn't) are
supposed to control a service if that service is running, regardless of the
reason.
If I understand well, the bug is in the behavior of the force-reload
parameter, that is often (but not always) an alias for restart (and so
is a bug for hundreds of packages?)
Which is really not related at all with the runlevel. The admin may have
started it manually, and the service still has to be reloaded in that case.
So if I have the daemon started by hand, or by some HeartBeat OCF
scripts (as in our case), possibly with different configurations and
parameters, the init script is supposed to [force-]reload it anyway,
even if this can change the way the daemons works due to different
configurations?
Can (must?) I control this via /usr/sbin/policy-rc.d?
It is not cleaner to skip the request at all?
Unfortunately, no.
It is not completely clear to me the reason, but maybe this is not an
argument to deal with a bug report, so if there is a reference may be
good.
Paolo Miotto
----------------------------------------------------------------------
SEMEL (SErvizio di Messaging ELettronico) - CSIT -Universita' di Udine
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
