-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Debian Lenny (5.0.9), Jenkins 1.434
Under debian Lenny, the /etc/init.d/jenkins status script always exit with return code 0, even it the service is not running. According to LSB standard, the return code should be the following:
- 0 program is running or service is OK;
- 1 program is dead and /var/run pid file exists;
- 3 program is not running.
Found on https://fedoraproject.org/wiki/FCNewInit/Initscripts#Init_Script_Actions as official LSB website is currently down.
This fixed status code is quite annoying if we rely on the init script for monitoring purpose.
[JENKINS-11306] Debian init script: status command exit code is always 0
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 141525 ] | New: JNJira + In-Review [ 189668 ] |
The Debian Wiki collects together relevant information at
http://wiki.debian.org/LSBInitScripts
In particular the final comment says that Debian policy diverges from LSB in that Debian always uses return code 0.
There is much discussion at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208010
It looks to me like current Debian behaviour/best practice is to return 0 as Jenkins currently does.