From: Joshua N Pritikin <jpritikin@pobox.com>
Subject: Re: service definition vs service activation
Date: Tue, 7 Mar 2006 10:51:24 +0530 [thread overview]
Message-ID: <20060307052124.GH6346@always.joy.eth.net> (raw)
In-Reply-To: <20060306215443.GA23824@dusk.harfang.homelinux.org>
On Mon, Mar 06, 2006 at 10:54:43PM +0100, Gilles wrote:
> > In summary, all this has just been a long-winded way of appealing
> > for a reconsideration of documenting /etc/sv as the service definition
> > directory for runit.
>
> As I hinted in a previous post (but without giving the arguments as you
> did), I think I agree with you ;-)
Agreed.
The definitions need to be on a writable volume because of runsv's
supervise state. /etc is not always writable.
next prev parent reply other threads:[~2006-03-07 5:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 16:05 runit-1.4.0 available Gerrit Pape
2006-03-06 19:13 ` service definition vs service activation Wayne Marshall
2006-03-06 21:54 ` Gilles
2006-03-07 5:21 ` Joshua N Pritikin [this message]
2006-03-07 18:35 ` Alex Efros
2006-03-08 5:18 ` Joshua N Pritikin
2006-03-16 10:46 ` Gerrit Pape
2006-03-08 15:40 ` Christian Holtje
2006-03-08 16:04 ` Joshua N Pritikin
2006-03-20 21:17 ` runit-1.4.1 available Gerrit Pape
2006-03-07 13:30 service definition vs service activation Joshua N Pritikin
2006-03-07 17:46 ` Joshua N Pritikin
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=20060307052124.GH6346@always.joy.eth.net \
--to=jpritikin@pobox.com \
/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).