supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Roy Lanek <lanek@novenine.com>
Subject: Re: Installing dnscache with runit, without other djb utils
Date: Thu, 28 Sep 2006 07:12:13 +0700	[thread overview]
Message-ID: <20060928001213.GA13416@cengkeh.novenine.com> (raw)

** Sorry for answering late

> I'd like to install djb's dnscache to run under my
> existing runit-based system.

** you can (it's working perfectly for me).

> In order to do so, it seems to require me to install
> a number of other djb utilities which have the same
> name as some of the runit-based symlinks: setuidgid,
> pgrphack, etc.

** no. My case:

/etc/dnscache
    with the usual inner structure (log, supervise, run) +

        /etc/dnscache/env
        /etc/dnscache/root
        /etc/dnscache/seed

    extra

env, root, seed like with the original dnscache
log and supervise like usual

drwxr-sr-x 2 root root   8 Jun 19 02:34 env
drwxr-x--- 3 root xxx    5 Jun 19 02:27 log
drwxr-sr-x 4 root root   4 Jun 19 02:21 root
-rwx------ 1 root root 395 Jun 19 14:51 run
-rw------- 1 root root 128 Sep 28 02:39 seed
drwx------ 2 root root   8 Sep 28 02:39 supervise

xxx is your groupid of choice from the runit family

run is:

#!/bin/sh
exec 2>&1
cd '/etc/dnscache' || exit 1

# -- seed:
umask 077
/bin/rm -f seed
/bin/dd if=/dev/urandom bs=128 count=1 > seed 2> /dev/null
    # -- "Linux has a good source of random data, use 128
    # -- bytes of it to pass it to 'dns_random_init' (via
    # -- 'seed')."^1

exec chpst -U yyy -e ./env -o 250 -d "$DATALIMIT" \
        /usr/bin/dnscache


# -- 1. The dnscache-conf program, djbdns' doc.



with yyy = your userid for dnscache (from the passwd)


run in supervise is:

#!/bin/sh
exec chpst -uxxx svlogd -tt main/dnscache

with xxx the same as above
and main as known. 


symbolic link to /etc/dnscache as usual


Hope I have given you enough info.

The only exception I know in which I had to really compile
daemontools--just to extract tai64n and tai64nlocal--is
uschedule, which I also use with great satisfaction under
runit. (You need also to set a bit up an environment, a
trivial task).

Cheers,

/Roy

P.S.

After a second thought, maybe it interests others too (I
have answered to the sender directly already).
-- 
########################     anjing menggonggong, kafilah tetap berlalu  
##### . slackware ######     the dogs are barking, the caravan moves on  
##### +-----linux ######  [illustrates useless protest, critic, or sarcasm] 
########################


             reply	other threads:[~2006-09-28  0:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  0:12 Roy Lanek [this message]
2008-07-18 14:20 ` Charlie Brady
  -- strict thread matches above, loose matches on Subject: below --
2008-07-19 18:15 lanek
     [not found] <49351.125.162.61.255.1216395759.squirrel@novenine.com>
2008-07-19 16:24 ` Charlie Brady
2008-07-19  6:02 lanek
2006-09-20 22:30 Lloyd Zusman
2006-09-20 23:49 ` Wayne Marshall
2006-09-21  0:07 ` Vincent Danen
2006-09-21  0:12 ` Charlie Brady
2006-09-21  0:44   ` Lloyd Zusman
2006-09-21  1:03     ` Charlie Brady
2006-09-21  1:28       ` Lloyd Zusman

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=20060928001213.GA13416@cengkeh.novenine.com \
    --to=lanek@novenine.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).