Re: Bug for sv status in lsb mode

[Gerrit Pape <pape@smarden.org>]

Erik Wright <erik <at> akoha.com> writes:
> 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 <at> 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 <at> 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 <at> domU-12-31-39-0C-1D-B1:~# dpkg -s runit
> Package: runit
> ...
> Version: 2.0.0-1ubuntu3.1
> root <at> domU-12-31-39-0C-1D-B1:~# cat /etc/issue
> Ubuntu 9.10 \n \l
> --------
> 
> Any ideas what might be causing this?

Hi, there was a bug discovered in this very thread, which has been fixed
in runit version 2.1.0:

  * sv.c: fix exit code of status command in lsb mode (thx Mathieu
    Poumeyrol)

If you upgrade to the latest version, it should work fine.

Regards, Gerrit.