Re: wrong exit code for sv status in lsb mode

From: David Mountney via supervision <>
Date: Fri, 4 Jan 2019 17:10:13 -0800

This looks like it's still a problem introduced in runit 2.1.2

If you have defined a log handler, only the status of the log handler is
returned by sv status.

Its not clear to me from the changelog why this change was made.

I guess, ideally if the service status was successful, you could then also
check the log status, but as it is now, if the service is down, but the log
is up, sv status reports all is well for its exit codes.

I've seen other references to this bug, where projects have reverted to the
previous runit version:

It would be ideal if we could just get this fixed.

> From: Fabian Ruff
> Date: Tue, 18 Aug 2015 23:33:50 +0200
> Tue, 18 Aug 2015 23:33:50 +0200
> Hi,
> I just noticed that the exit code of sv status in "lsb" mode is not 3 in
> all cases when
> the service is "down".
> The problem arises when a service defines a log handler. In that case the
> return code
> of svstatus print for the log process overwrites the return code of
> svstatus print of
> the actual supervised process (line 170 of sv.c).
> Is this intentional? Looks like a bug to me.
> Kind regards,
Received on Sat Jan 05 2019 - 01:10:13 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC