From: George Georgalis <george@galis.org>
To: supervision@list.skarnet.org
Subject: Re: FHS compatibility for daemontools/runit
Date: Mon, 19 May 2008 18:19:27 -0400 [thread overview]
Message-ID: <20080519221927.GA28511@sadie.duo> (raw)
In-Reply-To: <20080519095426.5deb95fb@alloy.copperisle.com>
On Mon 19 May 2008 at 09:54:26 AM +0000, Wayne Marshall wrote:
>It is trivial to obtain FHS compatibility with daemontools/runit.
>
>1) Install service definitions on /var, e.g.:
>
> /var/service.d/
>
>2) Setup the service activation directory in /etc, e.g.:
>
> /etc/service/
>
>3) Configure startup of svscan/runsvdir to monitor the service
>activation directory, /etc/service.
>
>4) To activate a service, symlink its service definition
>directory into the service activation directory:
>
> # cd /etc/service
> # ln -s /var/service.d/qmail-start
>
>That's all there is to it. All run-time files are created and
>maintained on /var, the root partition may be mounted read-only
>(after making service activation symlinks), it is both possible
>and sensible to keep multilogs within each respective service
>definition directory, and no other symlink gymnastics are
>required.
>
>For pure djb compatibility, symlink /service --> /etc/service.
>
What about run scripts in var? And there is this:
Applications must generally not add directories to the
top level of /var. Such directories should only be
added if they have some system-wide implication, and
in consultation with the FHS mailing list.
...from fhs-2.3.
// George
--
George Georgalis, information system scientist <IXOYE><
prev parent reply other threads:[~2008-05-19 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 9:54 Wayne Marshall
2008-05-19 22:19 ` George Georgalis [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=20080519221927.GA28511@sadie.duo \
--to=george@galis.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).