supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: /etc/runit vs /etc/sv vs /usr/share (Debian)
Date: Wed, 1 Feb 2006 15:33:04 +0000	[thread overview]
Message-ID: <20060201153304.32674.qmail@55005bbe423341.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20060201145445.GA12654@dusk.harfang.homelinux.org>

On Wed, Feb 01, 2006 at 03:54:45PM +0100, Gilles wrote:
> > 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"?

While I can provide a socklog-run package, I don't have control over
the 'other' packages.  And I'm afraid it's not that easy to convince
maintainers of 'other' packages to provide such a *-run package, at
least not short-term.  So the runit-services package is a (interims)
place to make the service directories available conveniently.  I would
be happy to remove them once they appear in a <service>-run package.
One could try by filing wishlist bugs against the corresponding
packages.

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

No, I recommend to have them _accessible_ through the service directory,
think of symlinks.

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

Maybe.  I personally don't care that much, and don't link them into
/var/service/.

Regards, Gerrit.


  reply	other threads:[~2006-02-01 15:33 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
2006-02-01 15:33     ` Gerrit Pape [this message]
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=20060201153304.32674.qmail@55005bbe423341.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).