Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jan 2009 16:14:22 +1100
From:      Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>
To:        roam@freebsd.org, freebsd-stable@freebsd.org
Subject:   How to get djbdns to start early enough to satisfy ntpd at boot?
Message-ID:  <20090115051422.GA59032@duncan.reilly.home>

next in thread | raw e-mail | index | archive | help
Hi there,

I've been a happy djbdns+tinydns user for many, many years.  I
want to keep using it, so answers of the form "bletch!  Use ISC
BIND the way BSD intended" will be ignored :-)

Having said that, one annoying consequence of my transition
some time ago to using ntpd, rather than just setting the clock
once-off with ntpdate as I used to, is that the /etc/rc.d
mechanism starts ntpd before /usr/local/etc/rc.d/svscan.sh
starts svscan, which starts /services/dnscache.  That wouldn't
matter if ntpd was a bit sensible and just kept trying to find
its nomminated servers, but it gives up and just sits there not
synchronising time from any reference.  So I have to remember to
manually "/etc/rc.d/ntpd restart" every time I reboot.

So: does anyone know how to modify the boot-time order so that
svscan starts at (or before) the point in the boot cycle where
BIND would, on other systems?  I suspect that it should be
possible by changing the PROVIDE: in svscan.sh to include one of
the things REQUIRE:'d by ntpd.  Or perhaps the REQUIRE: LOGIN in
svscan.sh is incompatible with the BEFORE: LOGIN in ntpd?

Has any other user of dnscache encountered and solved this
problem?

Cheers,

Andrew



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090115051422.GA59032>