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>
To: supervision@list.skarnet.org
Subject: Re: runit-1.9.0 available
Date: Tue, 13 May 2008 10:48:59 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080513T104459-914@post.gmane.org> (raw)
In-Reply-To: <48296B7C.20302@robinbowes.com>

Robin Bowes <robin-lists <at> robinbowes.com> writes:
> Gerrit Pape wrote:
> > When installing runit on a system that should comply with the Filesystem
> > Hierarchy Standard (FHS), neither /service/ nor /var/service/ should be
> > chosen, but /etc/service/.  It is recommended to create a compatibility
> > symlink /service pointing to /etc/service in this case.
> 
> Is this for the actual service configurations, or the directory 
> monitored by runsvdir-start ?

The latter.

> Are you sure this is FHS-compliant? Wouldn't /var/run/service be a 
> better location?

At Debian, which adheres to the FHS, we agreed that /etc/service/
doesn't conflict with the FHS, so yes.  /var/run/service is not
suitable, because /var/run/ may well be a ramdisk, and its content
is not guaranteed to survive a reboot.

Regards, Gerrit.

http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION




  reply	other threads:[~2008-05-13 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  9:28 Gerrit Pape
2008-05-13 10:20 ` Robin Bowes
2008-05-13 10:48   ` Gerrit Pape [this message]
2008-05-14 23:11     ` George Georgalis
2008-05-15 17:10       ` Charles Duffy
2008-05-16  1:25         ` Zachary Kotlarek
2008-05-16 12:55           ` Robin Bowes
2008-05-16 13:37             ` Radek Podgorny
2008-05-16 15:07         ` Charles Duffy

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=loom.20080513T104459-914@post.gmane.org \
    --to=pape@smarden.org \
    --cc=supervision@list.skarnet.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).