On Wed, Dec 12, 2007 at 01:08:42AM +1100, mufurcz wrote: Hi. > Greetings, > > A disk in one of the old firewalls (not exactly critical) failed (running > OpenBSD 2.9!), and I urgently > need a DNS server to work. Replaced the disk and installed 4.2. Starting > `named -g` (listing below), > produces a few surprising messages, like: > > a) line 3: BIND trying to load the configuration from /etc an not from > /var/named/etc (my understanding > was that the default -c option looks for the named.config in /var/named/etc > an not in /etc); AFAIK the originale,unmodified bind from OpenBSD runs in a chroot()ed environment under /var/named. So its root is really at /. So if it says it reads from /etc/named.conf it _REALLY_ reads from /var/named/etc/named.conf because of the chroot.
> b) lines 34 and 35: `could not open entropy source /dev/arandom: file not > found` and `using pre-chroot > entropy source /dev/arandom` complaining about a missing > /var/named/dev/arandom device. Same as above. /dev/arandom is _REALLY_ /var/named/dev/arandom. So just why not creating this device? cd /var/named/dev mknod arandom c 45 4 > What BIND has to do with the laws of thermo-dynamics? Can I safely ignore > the above messages. BIND needs /dev/arandom for some stuff like generating random IDs. > BTW, I am NOT a BIND expert! Neither do I ;) Oh and don't forget the chroot() thingy mentioned above. If you write to logfiles etc. they will get written to /var/named/var/log/... ! HTH, Andreas. -- Windows 95: A 32-bit patch for a 16-bit GUI shell running on top of an 8-bit operating system written for a 4-bit processor by a 2-bit company who cannot stand 1 bit of competition.
