supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Dean Hall <deanpence@gmail.com>
Subject: Re: runit directory organization
Date: Fri, 8 Apr 2005 14:45:41 -0400	[thread overview]
Message-ID: <bb16d53e050408114528300cf6@mail.gmail.com> (raw)
In-Reply-To: <000a01c53970$dd986680$6601a8c0@GHDESK>

On Apr 4, 2005 7:48 PM, Gregg Howe <gregg@astronumerics.com> wrote:
>  
> 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. 

As someone has noted already, runit and other djb-ish software usually
deliberately breaks FHS compatibility. I run gentoo myself and,
without editing every ebuild I install, I'm pretty much stuck with a
mostly FHS-compatible OS. Luckily, djb-ish stuff lets you do whatever
you want.

> 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)?

Here's the way I do it, though I'm sure many might dislike it:

- envdirs in /etc/envdir.d
- misc. configuration in /etc/config.d
- services in /var/service/{all,default,current}

I don't use /etc/runit at all.

Don't worry too much about what directories in which to put stuff.
It's really up to you.


d
-- 
http://deanpence.com


  parent reply	other threads:[~2005-04-08 18:45 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 [this message]
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=bb16d53e050408114528300cf6@mail.gmail.com \
    --to=deanpence@gmail.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).