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: /service vs /var/service vs /etc/service
Date: Sat, 19 Apr 2008 13:54:14 +0000	[thread overview]
Message-ID: <20080419135414.12570.qmail@4bcbc2195532ad.315fe32.mid.smarden.org> (raw)
In-Reply-To: <4809F52F.1020306@robinbowes.com>

On Sat, Apr 19, 2008 at 02:35:43PM +0100, Robin Bowes wrote:
> Gerrit Pape wrote:
>> 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.
>
> Out of interest, where do you/Debian/others put the actual service  
> directories, i.e. containing the run file and log dir? I currently use  
> /etc/sv/servicename and symlink to /var/service/

Me/Debian: /etc/sv/<service-name>, and the ./supervise symlinks point to
/var/lib/supervise/<service-name>[.log].  /var/run/ turned out to not be
appropriate, since it might be cleaned up on reboot, losing permission
changes possibly made to the directory and files in it.

Regards, Gerrit.


  reply	other threads:[~2008-04-19 13:54 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       ` /service vs /var/service vs /etc/service Gerrit Pape
2008-04-19 13:35         ` Robin Bowes
2008-04-19 13:54           ` Gerrit Pape [this message]
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=20080419135414.12570.qmail@4bcbc2195532ad.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).