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: /service vs /var/service vs /etc/service
Date: Sat, 19 Apr 2008 13:25:16 +0000	[thread overview]
Message-ID: <20080419132517.6752.qmail@7bcdc3a3e39f79.315fe32.mid.smarden.org> (raw)
In-Reply-To: <4809311F.3060804@robinbowes.com>

On Sat, Apr 19, 2008 at 12:39:11AM +0100, Robin Bowes wrote:
> It's a different way of doing things.
>
> To fit in with FHS, certain things should go in certain places. That's  
> the reason to do it "my" way. I'm not arguing that it's better, or  
> right, but this is the reason.

Hi, I'm in the same situation, Debian adheres strictly to the FHS.
Establishing /var/service apparently failed, runit in Debian used it
since 2002, it's runit's default since 2003.  But /var/service doesn't
comply with the FHS, and this will not change.

The Debian runit package now switched to /etc/service, and I'm about to
change runit to use /service by default, just as daemontools does.
daemontools in Debian, just like runit in Debian, uses /etc/service, and
recommends to create a compatibility symlink /service -> /etc/service.

To support putting the ./supervise/ directories into a different
location than the service directories, runit deals with dangling
symlinks as discussed.  For Debian I added the update-service(8) program
to help managing this, when using update-service(8) and sv(8) you don't
need to know about the location of the directory for services, /service,
/var/service, or /etc/service, and the symlinks are set up
automatically.  So servise directories managed with these tools comply
with the FHS.

I hope this will work out.

Regards, Gerrit.


  reply	other threads:[~2008-04-19 13:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 20:32 configurable path to ./supervise/ Mike
2008-04-18 21:41 ` Robin Bowes
2008-04-18 22:11   ` Alex Efros
2008-04-18 22:21     ` Charlie Brady
2008-04-18 22:30       ` Alex Efros
2008-04-18 22:48         ` Mike
2008-04-18 23:00         ` Charlie Brady
2008-04-18 23:39     ` Robin Bowes
2008-04-19 13:25       ` Gerrit Pape [this message]
2008-04-19 13:35         ` /service vs /var/service vs /etc/service Robin Bowes
2008-04-19 13:54           ` Gerrit Pape
2008-04-19 14:13             ` Robin Bowes
2008-04-19 17:40               ` Gerrit Pape
     [not found]             ` <283B46AC657546A883A45437109FE51D@home.internal>
2008-04-22 16:24               ` rehan khan

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=20080419132517.6752.qmail@7bcdc3a3e39f79.315fe32.mid.smarden.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).