Re: initscripts and fail states
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Should it really be a "failure" mode when a 'reload' (assuming the
> script supports that target) fails to reload the daemon configuration
> because the daemon isn't running? I don't want the service to start if
> it isn't already (hence force-reload isn't appropriate), but I want to
> make sure that, if the program is running, that it's running the latest
> and greatest configuration. Isn't that what 'reload' is for?
Debian policy does not seem to mention exit codes of init scripts:
http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
but LSB 1.3 has some return values specified for init scripts and the
actions that should be taken:
http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/iniscrptact.html
however it is still not clear if a 'reload' should start a service if it
is not running or if it a failure to 'reload' a service that is not
running. It is specified there that 'restart'-ing a service that is not
running should be a successful action.
- -- arthur - adejong@debian.org - http://people.debian.org/~adejong --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
iD8DBQE/+ByQVYan35+NCKcRAjkyAJ4y/dL/fe/gMiJNH91w0fIrD9pbmQCfYWhg
JW9hfTLyxpWp7TQdzKqAeNg=
=jFdM
-----END PGP SIGNATURE-----
Reply to: