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: runit directory organization
Date: Mon, 18 Apr 2005 19:30:24 +0000	[thread overview]
Message-ID: <20050418193039.22204.qmail@984e471ecf3311.315fe32.mid.smarden.org> (raw)
In-Reply-To: <000a01c53970$dd986680$6601a8c0@GHDESK>

On Mon, Apr 04, 2005 at 04:48:55PM -0700, Gregg Howe wrote:
> I have just installed runit in my lfs system and I am so grateful to
> be able to simplify managing services.
> 
> However, I am undecided as to how to organize the service file
> directories and I am wondering what works for others.  And whether
> anyone cares about whether or how the runit file organization should
> fit into the Linux FHS.

On Debian, I have the runit configuration including getty services in
/etc/runit/.  Other packages/services put their service directories into
/etc/ (or a subdirectory /etc/<package>/), and optionally provide a link
in /var/service/.  Logs are put into /var/log/.

> Ordinarily, I would have service start and finish scripts in /etc, yet
> the service hierarchy also contains pipes, flags, pid files, etc which
> seem more appropriate in /var.

You can make the ./supervise subdirectory in the service directory a
symlink to /var/run/<service> before enabling it for the first time.
runsv will follow the dangling symlink, and creates the directory in
/var/run/.  So you only have the configuration in /etc/.

Regards, Gerrit.


      parent reply	other threads:[~2005-04-18 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 23:48 Gregg Howe
2005-04-05  6:37 ` Alex Efros
2005-04-06 17:52 ` Csillag Tamás
2005-04-08 18:45 ` Dean Hall
2005-04-18 19:30 ` Gerrit Pape [this message]

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=20050418193039.22204.qmail@984e471ecf3311.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).