Re: PROPOSAL: init file actions (draft 4)
It seems reasonable to me to leave some space around the
status-specific exit codes (2-4 below) and the non-status exit codes
(5-9 below), since some other exit code for the `status' option may
turn out to be needed or desired. Why not use the following scheme:
code action meaning
---- ------ -------------------------------------------------------
0 all success (for "status", it means the program is running)
1 all unspecified error
2 status program dead, /var/lock lock file exists
3 status program stopped
4 status program dead, /var/run pid file exists
! 5-9 status reserved for future LSB use
! 10 all command line usage error
! 11 all unimplemented feature (e.g., reload is not implemented)
! 12 all permission denied
! 13 all program not installed
! 14 all configuration error
! 15-99 - reserved for LSB use
100-149 - reserved for distribution-specific use
150-199 - reserved for application-specific use
200-254 - reserved for LSB use
thus giving room for expansion.
--jim
%%%%%%%%%%%%%%% jim knoble %%%%%%%% jmknoble@pobox.com %%%%%%%%%%%%%%%%%
På 1999-Jun-21 klokka 19:08:13 -0700 skrivet Daniel Quinlan:
: Init files should return an exit status of zero if the action
: described by the argument has been successful. Otherwise, the exit
: status should be non-zero.
[...]
: Exit status codes:
:
: code action meaning
: ---- ------ -------------------------------------------------------
: 0 all success (for "status", it means the program is running)
: 1 all unspecified error
: 2 status program dead, /var/lock lock file exists
: 3 status program stopped
: 4 status program dead, /var/run pid file exists
: 5 all command line usage error
: 6 all unimplemented feature (e.g., reload is not implemented)
: 7 all permission denied
: 8 all program not installed
: 9 all configuration error
: 10-99 - reserved for LSB use
: 100-149 - reserved for distribution-specific use
: 150-199 - reserved for application-specific use
: 200-254 - reserved for LSB use
Reply to: