supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
To: supervision@list.skarnet.org
Subject: Re: wrong exit code for sv status in lsb mode
Date: Wed, 13 Mar 2019 08:04:07 +0000	[thread overview]
Message-ID: <20190313080407.5662.qmail@f0acb20213ddef.315fe32.mid.smarden.org> (raw)
In-Reply-To: <CAKHqFBz8=kSBrZHE79+4V_ov5LJ6D1OddDenOXpsWr2fPVNkdA@mail.gmail.com>

On Tue, Jan 08, 2019 at 08:19:30AM -0800, David Mountney via supervision wrote:
> The error was introduced in commit 5fe1bc773c2d979093fe4b1f3ecbbed5e6acdaf0
> "sv.c: properly format status command's output on failure cases."
> 
> Where the log status is being saved to the same variable as the service
> status. The quick fix would be to not record the log status for now:
> 
> $ git diff src/sv.c
> diff --git a/src/sv.c b/src/sv.c
> index 9003142..1676227 100644
> --- a/src/sv.c
> +++ b/src/sv.c
> @@ -167,7 +167,7 @@ int status(char *unused) {
>    }
>    else {
>      outs("; ");
> -    if (svstatus_get()) { rc =svstatus_print("log"); outs("\n"); }
> +    if (svstatus_get()) { svstatus_print("log"); outs("\n"); }
>    }
>    islog =0;
>    flush("");
> $

Thanks for the patch, David.

I'm looking forward to do a maintenance release of runit eventually and
am collecting patches.  I'm about to apply this one, has anyone applied
it already and can provide feedback?

Regards, Gerrit.


  reply	other threads:[~2019-03-13  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  1:10 David Mountney via supervision
2019-01-08  8:11 ` Gerrit Pape
2019-01-08 16:19   ` David Mountney via supervision
2019-03-13  8:04     ` Gerrit Pape [this message]
2019-03-13 20:32       ` David Mountney via supervision
2019-04-17 15:58       ` James Byrne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190313080407.5662.qmail@f0acb20213ddef.315fe32.mid.smarden.org \
    --to=pape@smarden.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).