public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: overseers@sources.redhat.com
Subject: Sourceware now running djbdns
Date: Tue, 27 Feb 2001 03:14:00 -0000	[thread overview]
Message-ID: <sibsrol6nb.fsf@daffy.airs.com> (raw)

Sourceware is now running djbdns, both the cache and the server.
Along the way, I upgraded daemontools and ucspi-tcp.

With luck, nobody will notice any difference.

Please let me know about any problems that arise.

For the record, I have appended my notes as to what I did.

Sourceware is now running svscan, which means that if we like we can
start using to support qmail, and even CVS.  svscan is a program which
ensures that other programs always keep running.  It provides a simple
if very concise interface via the svc program.

Ian

Download daemontools-0.70.tar.gz into /usr/local/src/qmail-support.
Unpacked it.
In daemontools-0.70: make
cp /usr/local/bin/multilog /usr/local/bin/multilog.old
In daemontools-0.70: make setup check

mkdir /sourceware/service
ln -s /sourceware/service /service
Added
    SV:2345:respawn:/usr/bin/env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service </dev/null >/dev/console 2>/dev/console
to the end of /etc/inittab.
Did kill -HUP 1 to start svscan.

rm /usr/local/bin/multilog.old

Noticed that /etc/rc.d/rc*.d/qmail are files, not symlinks as they
should be.
ln -sf ../init.d/qmail /etc/rc.d/rc2.d/S80qmail
ln -sf ../init.d/qmail /etc/rc.d/rc3.d/S80qmail
ln -sf ../init.d/qmail /etc/rc.d/rc4.d/S80qmail
ln -sf ../init.d/qmail /etc/rc.d/rc5.d/S80qmail
ln -sf ../init.d/qmail /etc/rc.d/rc0.d/K30qmail
ln -sf ../init.d/qmail /etc/rc.d/rc1.d/K30qmail
ln -sf ../init.d/qmail /etc/rc.d/rc6.d/K30qmail

Downloaded ucspi-tcp-0.88.tar.gz into /usr/local/src/qmail-support.
Unpacked it.
In ucspi-tcp-0.88: make
mv /usr/local/bin/tcpserver /usr/local/bin/tcpserver.old
In ucspi-tcp-0.88: make setup check
rm /usr/local/bin/tcpserver.old
rm /usr/local/bin/fixcr

mkdir /usr/local/src/djbdns
Downloaded djbdns-1.05.tar.gz into /usr/local/src/djbdns.
Unpacked it.
In djbdns-1.05: make
In djbdns-1.05: make setup check

mkdir /sourceware/djbdns

/usr/sbin/groupadd -g1779 djbdns
/usr/sbin/useradd -d/sourceware/djbdns -g1779 -s/bin/true -u 22786 dnscache
/usr/sbin/useradd -d/sourceware/djbdns -g1779 -s/bin/true -u 22787 dnslog

dnscache-conf dnscache dnslog /sourceware/djbdns/dnscache
echo 10000000 > /sourceware/djbdns/dnscache/env/CACHESIZE
echo 15000000 > /sourceware/djbdns/dnscache/env/DATALIMIT 

/usr/sbin/useradd -d/sourceware/djbdns -g1779 -s/bin/true -u 22788 tinydns

tinydns-conf tinydns dnslog /sourceware/djbdns/tinydns 205.180.83.71

Set up server files in /sourceware/djbdns/tinydns/root

/usr/sbin/useradd -d/sourceware/djbdns -g1779 -s/bin/true -u 22789 axfrdns

axfrdns-conf axfrdns dnslog /sourceware/djbdns/axfrdns /sourceware/djbdns/tinydns 205.180.83.71
In /sourceware/djbdns/axfrdns/tcp, change :deny to :allow
In /sourceware/djbdns/axfrdns: make

/etc/rc.d/init.d/named stop
ln -s /sourceware/djbdns/dnscache /service
ln -s /sourceware/djbdns/tinydns /service
ln -s /sourceware/djbdns/axfrdns /service

In /etc/rc.d: for i in rc3.d rc4.d rc5.d; do mv $i/S55named $i/K45named; done

Created /etc/cron.hourly/tinydns

                 reply	other threads:[~2001-02-27  3:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=sibsrol6nb.fsf@daffy.airs.com \
    --to=ian@airs.com \
    --cc=overseers@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).