supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: rehan khan <rehan.khan@dsl.pipex.com>
Cc: supervision@list.skarnet.org
Subject: RE: Customised control help
Date: Wed, 2 Jan 2008 09:41:34 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801020935480.9932@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <50F2BE60A0EF6D478B1BCC633DEC28CC01F704@server.home.internal>


On Wed, 2 Jan 2008, rehan khan wrote:

>>> 4) Is there a more detailed description of customised control somewhere?
>>
>> I think the man page of runsv is complete and accurate. What do you think
>> is missing? The source code might help you if you wish to learn more or to
>> confirm what you read in the man page.
>
> Heh, some of my questions might seem dumb but I have read ALL the docs many
> times over. I have found the documentation to be 100% complete. However
> sometimes it can be difficult to interpret for all situations (or the particular
> situation that is in my head :). For example in the above documentation example
> it might be better to say that the examples given are special cases or that they
> are examples that apply to all the options.

I think it reads clearly that 'o', 'd' and 'x' are special cases, and that 
'for each' really does mean 'for each', but YMMV.

> Perhaps also to expand on the description ...

How would the description be expanded if it is already complete?

> and to describe the exit codes 
> (even if it is repeated from elsewhere).

The exit codes of runsv are clearly stated. The interpretation of zero 
exit status from custom control scripts also seems clearly stated to me.

  "If the program exits with return code 0, runsv refrains from sending the
   service the corresponding signal."

What would you express differently?


  parent reply	other threads:[~2008-01-02 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01  8:27 Rehan Khan
2008-01-01 10:29 ` KORN Andras
2008-01-01 16:29 ` Charlie Brady
     [not found] ` <14AE52C8045C4D1F9AC27FD137DA0657@home.internal>
2008-01-02  6:44   ` rehan khan
2008-01-02 10:42     ` KORN Andras
2008-01-02 14:41     ` Charlie Brady [this message]
     [not found]     ` <0DEDB6FEF7B44A7C8C121C2E41C63F43@home.internal>
2008-01-02 17:03       ` rehan khan
2008-01-02 17:37         ` Charlie Brady
     [not found]         ` <CE0657F3ABAE4CE5B8C8E594928A8067@home.internal>
2008-01-03  4:33           ` rehan khan

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=Pine.LNX.4.64.0801020935480.9932@e-smith.charlieb.ott.istop.com \
    --to=charlieb-supervision@budge.apana.org.au \
    --cc=rehan.khan@dsl.pipex.com \
    --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).