From: "Csillag Tamás" <cstamas@digitus.itk.ppke.hu>
Cc: supervision@list.skarnet.org
Subject: Re: runit directory organization
Date: Wed, 6 Apr 2005 19:52:52 +0200 [thread overview]
Message-ID: <20050406175252.GI6177@digitus> (raw)
In-Reply-To: <000a01c53970$dd986680$6601a8c0@GHDESK>
Hi
On 04/04, 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.
>
> 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
I put each service in /var/srv I have /service which is symlinked to
/var/service. If I want to set-up a new service I put it into /var/srv
then symlink it to /service.
runsvdir watches /var/service
(The symlink is just for my own preference.)
This is better (IMHO) because I do not want to mess with log directories in
every dir. I mean log/run contains:
#!/bin/sh
exec chpst -u log svlogd -tt ./main
I do not have to keep up the same structure for log files.
And log files must not go to /etc.
--
What's the most effective Windows NT remote management tool?
A car.
cstamas
next prev parent reply other threads:[~2005-04-06 17:52 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 [this message]
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=20050406175252.GI6177@digitus \
--to=cstamas@digitus.itk.ppke.hu \
--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).