supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: TheOldFellow <theoldfellow@gmail.com>
Subject: Re: "djbdns" under "runit" (Debian)?
Date: Mon, 16 May 2005 20:43:47 +0100	[thread overview]
Message-ID: <4288F7F3.7030607@gmail.com> (raw)
In-Reply-To: <20050516001901.GA7888@harfang.homelinux.org>

Gilles wrote:
> Hello.
> 
> 
> Is it possible to run the "djbdns" suite under "runit"
> instead of "daemontools"?
> [I'd guess the answer is yes, as "runit" is introduced 
> as a replacement for "daemontools".]
> 
> If so, there seems to be a dependency problem in Debian:
> "djbdns-installer" depends on "daemontools" (and "runit"
> does not provide "daemontools").
> 
> Is this right?
> How to proceed?

I have djbdns running under runit on my workstation.  I installed the
programs in /usr/sbin.  I created a new user (dnscache) and group (dns)
and ran:

dnscache-config dnscache root /etc/dnscache

to create the /etc/dnscache service directory, and then re-wrote the
service directory like this:

run:
#!/bin/sh
# link stdout and stderr, so they both get logged
exec 2>&1
# put the file seed on the stdin file descriptor, so that dnscache can
# read it
exec <seed
# run dnscache with the envars in ./env
exec chpst -e ./env /usr/sbin/dnscache

log/run:
#!/bin/sh
exec svlogd -tt /var/log/dnscache

Note that I'm running the logging process as root.  I added GID and UID
files to the env directory.  This sacrifices a couple of the limits that
DJB's scripts uses, but these could be added back using chpst options, I
just haven't got round to it yet.

It works well for me.

R.


  parent reply	other threads:[~2005-05-16 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  0:19 Gilles
2005-05-16  0:30 ` mike
2005-05-16  0:57   ` Gilles
2005-05-16  2:08     ` mike
2005-05-16 19:55       ` Csillag Tamás
2005-05-16  1:13   ` Charlie Brady
2005-05-16  1:53     ` Gilles
2005-05-16  2:22     ` mike
2005-05-16 19:43 ` TheOldFellow [this message]
2005-05-17 13:20   ` Gilles
2005-05-17 13:49     ` 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=4288F7F3.7030607@gmail.com \
    --to=theoldfellow@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).