supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gilles <gilles@harfang.homelinux.org>
Subject: Re: /etc/runit vs /etc/sv vs /usr/share (Debian)
Date: Wed, 1 Feb 2006 15:54:45 +0100	[thread overview]
Message-ID: <20060201145445.GA12654@dusk.harfang.homelinux.org> (raw)
In-Reply-To: <20060201142806.25684.qmail@4ca2ca9055810d.315fe32.mid.smarden.org>

Hi.

> > 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.
> 

As the first reading on how things should be set up, maybe this page
should be updated.

> > 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. 

Again, the above page makes one think that you think the opposite.

> Initially I thought they should just go
> into /etc/, 

But that would have mixed with the server programs config files!  No?

> 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.
>

But why having some services in their own package "<service>-run" and
others mixed in "runit-services"?

> 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>/.
> 

Definitely fine for "run" and "log/run", but do you really recommend having
the log files in there too?  Those files can grow and eat a large amount
of the root partition's space!  I thought a better place would be

  /var/log/service/<service>

or with the newly proposed name

  /var/log/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.
> 

There, you said "for actual use", which was exactly my point in the
previous mail:  Not all services in the package "runit-services"
will be actually installed on the system:  For those unwanted services,
having a directory under "/etc/sv" might be construed as a little
bit "messy" (or at best, misleading).


Best,
Gilles


  reply	other threads:[~2006-02-01 14:54 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
2006-02-01 14:54   ` Gilles [this message]
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=20060201145445.GA12654@dusk.harfang.homelinux.org \
    --to=gilles@harfang.homelinux.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).