supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Gregg Howe" <gregg@astronumerics.com>
Subject: runit directory organization
Date: Mon, 4 Apr 2005 16:48:55 -0700	[thread overview]
Message-ID: <000a01c53970$dd986680$6601a8c0@GHDESK> (raw)

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

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.

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.  Or is this the kind of information that is destined for /svc (I am not really sure what /svc is for)?

I also will be setting up different service configurations, which I suppose are like runlevels.  But the description of using runsvchdir shows the svdirs (current, previous, etc) back in /etc rather than /var.  This confuses me.  Perhaps someone could explain how they organize their service directories, svdir directories and run scripts.

Gregg Howe

[-- Attachment #2: Type: text/html, Size: 1722 bytes --]

             reply	other threads:[~2005-04-04 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 23:48 Gregg Howe [this message]
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

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='000a01c53970$dd986680$6601a8c0@GHDESK' \
    --to=gregg@astronumerics.com \
    /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).