From: Toni Mueller <toni.mueller@oeko.net>
Subject: Re: daemon under runit?
Date: Thu, 14 Dec 2006 14:02:59 +0100 [thread overview]
Message-ID: <elri21$71s$2@sea.gmane.org> (raw)
In-Reply-To: <20061206134616.GA17175@home.power>
Alex Efros wrote:
> On Tue, Dec 05, 2006 at 11:34:42PM +0100, Toni Mueller wrote:
>> something like "sv down service". Unfortunately, in most cases, this
>> does not seem to work - the control/t script is not accessed when I
>> issue 'sv down service' (as "ls -lta" shows). One of the problems is
>
> You should use control/d instead of control/t if you wish to catch `sv down`.
Well, the man page says that control/t is executed before d or x on
either 'down' or 'exit'. From http://smarden.sunsite.dk/runit/runsv.8.html:
"On command d first service/control/t is checked, and then
service/control/d. On command x first service/control/t is checked, and
then service/control/x."
> It's usually simple enough to patch any program to not fork.
That's what I eventually did.
Thank you!
Best,
--Toni++
prev parent reply other threads:[~2006-12-14 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 22:34 Toni Mueller
2006-12-06 13:46 ` Alex Efros
2006-12-14 13:02 ` Toni Mueller [this message]
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='elri21$71s$2@sea.gmane.org' \
--to=toni.mueller@oeko.net \
/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).