[CLUG-tech] djbdns problems

Neil Muller neil at dip.sun.ac.za
Wed Feb 1 13:37:56 SAST 2006


On Wed, Feb 01, 2006 at 01:17:49PM +0200, Jacobus Brink wrote:
> Yes.
> #grep Gdnslog /etc/passwd
> Gdnslog:x:503:503::/home/Gdnslog:/bin/bash
> # grep Gdnscache /etc/passwd
> Gdnscache:x:514:514::/home/Gdnscache:/bin/bash
> >Then the log directory should exist under /var/service/dnscache
> I  must have messed up somewhere.

One approach is to create the log directory manually:

atop dnscahe
mkdir /etc/dnscache/log
mkdir /etc/dnscache/log/main
echo "#!/bin/sh: > /etc/dnscache/log/run
echo "exec setuidgid Gdnslog multilog t ./main" >> /etc/dnscache/log/run
chmod 755 /etc/dnscache/log/run
chown Gdnslog: /etc/dnscache/log/main
chmod g+s /etc/dnscache/log/main

Then restart the dnscahe service. svscan is meant to pick up the log
directory automatically and start the multilog process witha pipe
between it and the the dnscache process.

(/etc/dnscache/log may also need a supervise directory, mode 2700, owned
by root, but, IIRC, that should be automatically created).

If this doesn't give any useful logging output, it may be useful to
take dnscache down and attach strace to the svscan process qwhen you
bring dnscache back up, to see what exactly it's trying to do and what
fails.

-- 
Neil Muller  email: neil at dip.sun.ac.za 

Department of Applied Mathematics, University of Stellenbosch


More information about the Clug-tech mailing list