supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charles Duffy <Charles_Duffy@messageone.com>
To: supervision@list.skarnet.org
Subject: Re: runit-1.9.0 available
Date: Thu, 15 May 2008 12:10:43 -0500	[thread overview]
Message-ID: <g0hqpn$n33$1@ger.gmane.org> (raw)
In-Reply-To: <20080514231129.GH12997@run.duo>

George Georgalis wrote:
> On Tue 13 May 2008 at 10:48:59 AM +0000, Gerrit Pape wrote:
>> 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.
> 
> Why not /etc/service as a default for all systems?
> 
> (as I speculate it's related to /etc/opt : Configuration files for /opt)

I've built netbooting/embedded systems where /etc was mounted read-only. 
Putting the run, check, supervise and finish scripts there makes sense 
-- but it would be nice if the supervise directories could be split out 
and stored elsewhere (presumably on tmpfs) in such environments.



  reply	other threads:[~2008-05-15 17:10 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
2008-05-14 23:11     ` George Georgalis
2008-05-15 17:10       ` Charles Duffy [this message]
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='g0hqpn$n33$1@ger.gmane.org' \
    --to=charles_duffy@messageone.com \
    --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).