From: Mathieu Poumeyrol <kali@zoy.org>
To: Gerrit Pape <pape@smarden.org>
Cc: supervision@list.skarnet.org
Subject: Re: Bug for sv status in lsb mode
Date: Fri, 17 Jul 2009 12:02:05 +0200 [thread overview]
Message-ID: <74FC29D4-E338-49E2-8461-91BDD25FAD67@zoy.org> (raw)
In-Reply-To: <loom.20090717T090207-38@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]
Le 17 juil. 09 à 11:08, Gerrit Pape a écrit :
> 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?
Hello,
the man page is fine. And I aggree the behaviour you demounstrate is
correct.
The problem I exhibited and tracked is only visible for services that
use a logging script, as the function that will change the value of
the "r" global is only called if the service has a logging service...
# tree /etc/service/that-one-does-not-work
/etc/service/that-one-does-not-work
|-- log
| |-- main
| | |-- current
| | `-- lock
| |-- run
| `-- supervise
| |-- control
| |-- lock
| |-- ok
| |-- pid
| |-- stat
| `-- status
|-- run
`-- supervise
|-- control
|-- lock
|-- ok
|-- pid
|-- stat
`-- status
# ./that-one-does-not-work status ; echo $?
down: that-one-does-not: 8s, normally up; run: log: (pid 11444) 37s
0
next prev parent reply other threads:[~2009-07-17 10:02 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
2009-07-13 14:20 ` Charlie Brady
2009-07-17 9:08 ` Gerrit Pape
2009-07-17 10:02 ` Mathieu Poumeyrol [this message]
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=74FC29D4-E338-49E2-8461-91BDD25FAD67@zoy.org \
--to=kali@zoy.org \
--cc=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).