supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: runit on debian sid success, and questions
Date: Sat, 15 Jan 2005 16:07:15 +0000	[thread overview]
Message-ID: <20050115160620.15074.qmail@77689dde8fcfbc.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20050114120829.A11970@recycle.lbl.gov>

On Fri, Jan 14, 2005 at 12:08:29PM -0800, Larry Doolittle wrote:
> I have my debian sid amd64 system converted to runit-1.05.
Good ;-).

> I'm not done setting everything up, but at the moment my
> system is running about as well as it did before the change.
> 
> $ ls /var/service
> boa  getty-5  getty-6  klogd  ntpclient  qmail  socklog  sshd  xfs
> $
> 
> The only (non-kernel) daemons left running _not_ under runsvdir
> are udevd, portmap, and gconfd-2.  Vixie cron and I aren't getting
> along very well at the moment, it's not running at all.  :-p

See here for examples for portmap and Debian's cron:
 http://smarden.org/runit/runscripts.html#portmap
 http://smarden.org/runit/runscripts.html#cron

> Here are my questions (so far) about runit and friends:
> 
> In the debian kit, most static files are in /etc/runit,
> while dynamic files are in /var.  A forest of symlinks
> connects the two "databases".  One exception to that rule
> is the log configuration file, in /var/log/foo/config.
> Is this purposeful and/or unavoidable?

Since the filename always is ``config'' it must be associated with the
log directory, but you can of course make it a symlink if you like.

> The process of setting up service directories is tedious.
> It's a little late for me, but I can imagine automating some
> of the creation and maintenance process.  Maybe even (gasp)
> a GUI.  Are you aware of any efforts in this direction?

No, but if anyone goes for it, I would be interested.

Regards, Gerrit.


  reply	other threads:[~2005-01-15 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 20:08 Larry Doolittle
2005-01-15 16:07 ` Gerrit Pape [this message]
2005-01-19  1:13 Larry Doolittle
2005-01-19  3:59 ` Dean Hall
2005-01-19 10:03   ` Milan P. Stanic
2005-01-19  6:08 ` Larry Doolittle
2005-01-19 21:09   ` Thomas Schwinge
2005-01-19  6:39 ` Dean Hall
2005-01-23 12:23 ` Gerrit Pape
2005-01-19  6:12 Larry Doolittle
2005-01-19 21:07 ` Thomas Schwinge
2005-01-19 21:53   ` Larry Doolittle
2005-01-20 22:55 ` Vincent Danen

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=20050115160620.15074.qmail@77689dde8fcfbc.315fe32.mid.smarden.org \
    --to=pape@smarden.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).