Re: Bug#426877: Clarify what "sensible behaviour" is for init scripts

are right. Anyway I consider it a bit complex and the fact is that various Debian init scripts return 1 in the above case. Thanks for all. -- Iñaki Baz Castillo <[EMAIL PROTECTED]>

Re: Bug#426877: Clarify what "sensible behaviour" is for init scripts

n # 0 if daemon has been stopped # 1 if daemon was already stopped # 2 if daemon could not be stopped 2008/7/6, Russ Allbery <[EMAIL PROTECTED]>: > "\"Iñaki" Baz Castillo" <[EMAIL PROTECTED]> writes: > >> Op, sorry, I m

Re: Clarify what "sensible behaviour" is for init scripts

that is already running" but this is the default behaviour of Debian init scripts (dince --oknodo is optional and of course not always used). Thanks for your comments. Best regards. -- Iñaki Baz Castillo <[EMAIL PROTECTED]>

Re: Clarify what "sensible behaviour" is for init scripts

ounter > bad init scripts, please report bugs against the offending packages. In the above case which is the "bad" init script?: - lighttpd uses LSB specs. - apache2 uses Debian specs. Regards. -- Iñaki Baz Castillo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: Bug#426877: dpkg: Option "--oknodo" should be the default behaviour for "start-stop-daemon" (LSB specs)

people start services manually or they are started when the system swithes on, so return code is not so important. But in case of service daemon (as HeartBeat that handles when to start or stop a service) these return code becomes important and being LSB compliant is, IMHO, the best way. J