From: Gerrit Pape <pape@smarden.org>
Subject: Re: /etc/runit vs /etc/sv vs /usr/share (Debian)
Date: Wed, 1 Feb 2006 14:28:06 +0000 [thread overview]
Message-ID: <20060201142806.25684.qmail@4ca2ca9055810d.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20060201135409.GA10941@dusk.harfang.homelinux.org>
On Wed, Feb 01, 2006 at 02:54:09PM +0100, Gilles wrote:
> The "runit" documentation on the web site seems to
> recommend to install the service directory below
> "/etc/runit", while the new "runit-services" (for
I don't think it recommends it, but puts the default getty-5 service
directory in there, yes.
> Debian) installs them in "/etc/sv".
> Why the difference?
/etc/runit/ also is the place for the stage 1,2,3 scripts, and the magic
files stopit, reboot, ctrlaltdel. I don't think it's a good place to
put the service directories. Initially I thought they should just go
into /etc/, but in the style of the new sv program, I decided to now
recommend the /etc/sv/ directory. I'm in the progress of moving the
getty-? service directories and other (such as provided by socklog-run,
bcron-run, twoftpd-run, ...) into /etc/sv/ too.
After all it's just personal preference. I prefer to have the service's
configuration (including run scripts) and logs all accessible through a
single directory, now /etc/sv/<service>/.
/usr/share/ should be good for examples or template service directories,
but for actual use, they should be somewhere in /etc/, where
configuration files usually belong.
Regards, Gerrit.
next prev parent reply other threads:[~2006-02-01 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 13:54 Gilles
2006-02-01 14:28 ` Gerrit Pape [this message]
2006-02-01 14:54 ` Gilles
2006-02-01 15:33 ` Gerrit Pape
2006-02-01 17:52 ` Gilles
2006-02-01 17:15 ` Vincent Danen
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=20060201142806.25684.qmail@4ca2ca9055810d.315fe32.mid.smarden.org \
--to=pape@smarden.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).