From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: rehan khan <rehan.khan@dsl.pipex.com>
Cc: Mike Buland <mike@geekgene.com>, supervision@list.skarnet.org
Subject: RE: using runit as init
Date: Thu, 10 Jan 2008 20:28:06 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801102023430.9932@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <50F2BE60A0EF6D478B1BCC633DEC28CC082B1F@server.home.internal>
On Thu, 10 Jan 2008, rehan khan wrote:
>
> Although the dummy process resolves this particular problem it's not
> very clean.
"this particular problem"? You haven't quoted anything, so we don't know
which particular problem is.
> I would prefer not to have processes knocking about which do
> nothing.
I'm guessing you are referring to my suggestion of a program which calls
paus().
> Putting an 'sv d .' in the finish script seems to be the best solution
> to run once scripts run by runsvdir.
Yes, that sounds reasonable. That wouldn't be usable with daemontools,
however. It also means that 'sv t .' would be a no-op, so wouldn't be
usable with an init script wrapper which translated "service thing
restart" to 'sv t /service/thing".
> I still think that a mechanism built into the runsvdir to handle run
> once scripts would be better.
Perhaps.
next prev parent reply other threads:[~2008-01-11 1:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 20:51 Bernhard Graf
2008-01-04 0:22 ` Mike Buland
2008-01-05 0:06 ` Bernhard Graf
[not found] ` <12EC84FDD73F4BD8A78E7501EB19F1E2@home.internal>
2008-01-05 7:45 ` rehan khan
2008-01-05 23:17 ` Bernhard Graf
2008-01-08 7:11 ` Vincent Danen
2008-01-08 22:28 ` Bernhard Graf
2008-01-09 2:05 ` Vincent Danen
2008-01-09 23:06 ` Bernhard Graf
2008-01-09 23:34 ` Mike Buland
2008-01-09 23:51 ` Charlie Brady
2008-01-10 9:22 ` Bernhard Graf
2008-01-10 9:20 ` Bernhard Graf
2008-01-10 20:06 ` Mike Buland
2008-01-11 7:58 ` Bernhard Graf
2008-01-11 14:30 ` Mike Buland
2008-01-12 10:18 ` Bernhard Graf
2008-01-12 17:13 ` supervising (Re: using runit as init) Charlie Brady
2008-01-12 17:32 ` supervising mysql (Re: supervising (Re: using runit as init)) Charlie Brady
2008-01-13 4:40 ` using runit as init Vincent Danen
2008-01-13 15:36 ` Charlie Brady
2008-01-13 18:28 ` Mike Buland
2008-01-13 18:39 ` Charlie Brady
2008-01-13 18:49 ` Mike Buland
2008-01-14 3:55 ` Vincent Danen
2008-01-14 15:11 ` Charlie Brady
2008-01-14 15:21 ` Vincent Danen
[not found] ` <6A64B0D384404190ACB76E0A376CD148@home.internal>
2008-01-13 21:06 ` rehan khan
2008-01-14 3:53 ` Vincent Danen
[not found] ` <CDFFB8AF013F4762AE02CF6A1BDCB27A@home.internal>
2008-01-13 10:35 ` rehan khan
2008-01-14 3:50 ` Vincent Danen
2008-01-13 18:52 ` Mike Buland
[not found] ` <85040AD9CA634253A8FDB9F7DA6BD200@home.internal>
2008-01-10 22:08 ` rehan khan
2008-01-11 1:28 ` Charlie Brady [this message]
[not found] ` <C1A5323F485E4A75B75ADB58B664E35E@home.internal>
2008-01-10 21:56 ` rehan khan
2008-01-09 23:35 ` KORN Andras
2008-01-10 8:39 ` Bernhard Graf
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.0801102023430.9932@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=mike@geekgene.com \
--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).