supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Mathieu Poumeyrol <kali@zoy.org>
To: Mathieu Poumeyrol <kali@zoy.org>
Cc: Charlie Brady <charlieb-supervision@budge.apana.org.au>,
	supervision@list.skarnet.org
Subject: Re: Bug for sv status in lsb mode
Date: Mon, 13 Jul 2009 16:18:36 +0200	[thread overview]
Message-ID: <17A739BC-94BA-4611-A523-6978934F0D61@zoy.org> (raw)
In-Reply-To: <94175859-2733-4ACF-85E9-DD5FF627F23B@zoy.org>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]


Le 13 juil. 09 à 16:13, Mathieu Poumeyrol a écrit :
>
> Le 13 juil. 09 à 15:42, Charlie Brady a écrit :
>>
>> On Mon, 13 Jul 2009, Mathieu Poumeyrol wrote:
>>
>>> I have tracked down a bug in the lsb-compatible code for sv  
>>> status:  sv return 0 even if the service is down.
>>
>> What makes you think that sv status should return non-zero if the  
>> service is down? I see nothing to suggest that here:
>>
>> http://smarden.sunsite.dk/runit/sv.8.html
>
>
> 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.

  reply	other threads:[~2009-07-13 14:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  8:00 Mathieu Poumeyrol
2009-07-13 13:42 ` Charlie Brady
2009-07-13 14:13   ` Mathieu Poumeyrol
2009-07-13 14:18     ` Mathieu Poumeyrol [this message]
2009-07-13 14:20       ` Charlie Brady
2009-07-17  9:08       ` Gerrit Pape
2009-07-17 10:02         ` Mathieu Poumeyrol
2009-07-17 11:08           ` Gerrit Pape
2009-07-19 14:52         ` sv sometimes won't issue down request Earl Chew
2009-07-19 17:14           ` svwaitup races with sv Earl Chew
2009-07-24 20:31             ` Charlie Brady
2009-07-24 20:35               ` Earl Chew
2009-07-24 20:18           ` sv sometimes won't issue down request (specifically, after 'sv once xxx') Charlie Brady
2009-07-24 20:38             ` Earl Chew
2009-07-24 21:01               ` Charlie Brady
2009-07-25 19:49                 ` Joan Picanyol i Puig
2009-07-27  9:09           ` sv sometimes won't issue down request Gerrit Pape
2009-07-27 17:39             ` Earl Chew
2010-05-31 19:54         ` Bug for sv status in lsb mode Erik Wright
2010-06-03  9:04           ` Gerrit Pape
2010-06-03 14:12             ` Erik Wright

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=17A739BC-94BA-4611-A523-6978934F0D61@zoy.org \
    --to=kali@zoy.org \
    --cc=charlieb-supervision@budge.apana.org.au \
    --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).