Re: Bug for sv status in lsb mode

[Gerrit Pape <pape@smarden.org>]

Mathieu Poumeyrol <kali <at> zoy.org> writes:
> Le 13 juil. 09 à 16:13, Mathieu Poumeyrol a écrit :
> > Le 13 juil. 09 à 15:42, Charlie Brady a écrit :
> > It's not explicit here, but required for LSB compliance.
> >
> > see
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
> >
> > As a matter of fact, sv code looks like it is meant to achieve this,  
> > but fails because of the side effect on the "r" global.
> 
> Sorry, it is actually explicit in the "Exit codes" last paragraph...
> 
> If the command is status, it exits 3 if the service is down, and 4 if  
> the status is unknown. It exits 2 on wrong usage, and 151 on error.

Hi, this is a bug in the documentation then, the complete paragraph is

 If  sv  is called with a base name other than sv, it exits 1 on timeout
 or trouble sending the command.  If the command is status, it  exits  3
 if  the service is down, and 4 if the status is unknown.  It exits 2 on
 wrong usage, and 151 on error.

These exit codes only apply if sv is called with a different basename.

 # sv stop getty-5
 ok: down: getty-5: 0s, normally up
 # ln -s $(which sv) /tmp/getty-5
 # /tmp/getty-5 status
 down: getty-5: 4s, normally up
 # echo $?
 3
 #

Any suggestions on how to improve the man page?

Thanks, Gerrit.