Re: Bug for sv status in lsb mode

[Erik Wright <erik@akoha.com>]

Gerrit Pape <pape <at> smarden.org> writes:

> 
> 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.
> 
> 


Hi,

This is a follow-up to a thread from last summer. Mathieu Poumeyrol reported
that 'sv status' returned 0 even when the service was down. Gerrit replied that
this was expected behaviour when sv is called with a basename of 'sv'.

Unfortunately, I'm seeing this behaviour even when calling sv with another
basename. To illustrate, here is a shell session snippet on Ubuntu:

--------
root@domU-12-31-39-0C-1D-B1:~# ls -l /etc/init.d/celeryd 
lrwxrwxrwx 1 root root 11 2010-05-14 18:42 /etc/init.d/celeryd -> /usr/bin/sv
root@domU-12-31-39-0C-1D-B1:~# /etc/init.d/celeryd status; echo $?
down: celeryd: 1576s, normally up; run: log: (pid 711) 1043375s
0
root@domU-12-31-39-0C-1D-B1:~# dpkg -s runit
Package: runit
...
Version: 2.0.0-1ubuntu3.1
root@domU-12-31-39-0C-1D-B1:~# cat /etc/issue
Ubuntu 9.10 \n \l
--------

Any ideas what might be causing this?

Thanks,

Erik