From: Christian Holtje <list.supervision@docwhat.gerf.org>
Subject: Re: service definition vs service activation
Date: Wed, 08 Mar 2006 10:40:44 -0500 [thread overview]
Message-ID: <440EFAFC.3050800@docwhat.gerf.org> (raw)
In-Reply-To: <20060306111338.2d8151ff@alloy.copperisle.com>
Wayne Marshall wrote:
> However I would also say that, no matter the naming conventions one
> chooses, there is good reason for keeping service definition
> directories on the /var partition. Maybe this has been hashed to death
> elsewhere, but on many systems the /var partition is specifically
> suited to hosting log files and dynamic runtime data, while /etc is
> usually on the root partition and configured for static data.
>
Maybe the dynamic data should be shunted elsewhere.
Example: add extra arguments to svlogd that tell it where to put the
"real" log files to... svlogd could maintain symlinks from the real log
files to the /etc/sv/thingy/log/ directory.
I don't much care about the supervise being in /etc/sv/thingy...it's
annoying, but I can live with it. The lock file is a little more
annoying, but it is just a part of svlog and probably can be moved as
well....
Ciao!
--
A man's only as old as the woman he feels.
-- Groucho Marx
The Doctor What: Un-Humble http://docwhat.gerf.org/
docwhat *at* gerf *dot* org KF6VNC
next prev parent reply other threads:[~2006-03-08 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 16:05 runit-1.4.0 available Gerrit Pape
2006-03-06 19:13 ` service definition vs service activation Wayne Marshall
2006-03-06 21:54 ` Gilles
2006-03-07 5:21 ` Joshua N Pritikin
2006-03-07 18:35 ` Alex Efros
2006-03-08 5:18 ` Joshua N Pritikin
2006-03-16 10:46 ` Gerrit Pape
2006-03-08 15:40 ` Christian Holtje [this message]
2006-03-08 16:04 ` Joshua N Pritikin
2006-03-20 21:17 ` runit-1.4.1 available Gerrit Pape
2006-03-07 13:30 service definition vs service activation Joshua N Pritikin
2006-03-07 17:46 ` Joshua N Pritikin
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=440EFAFC.3050800@docwhat.gerf.org \
--to=list.supervision@docwhat.gerf.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).