Date: Mon, 15 Nov 1999 05:32:06 -0500 (EST) From: matt <matt@BabCom.ORG> To: FreeBSD-STABLE <stable@FreeBSD.ORG> Subject: chroot & bind 8.2.2-P5 Message-ID: <Pine.BSF.4.20.9911150526100.50886-100000@s01.arpa-canada.net>
next in thread | raw e-mail | index | archive | help
Hello, I just upgraded bind to 8.2.2-P5, and decided that with the recent problems, I would chroot bind. This went very well, I had no problems after following the directions at http://www.psionic.com/papers/dns/dns-openbsd/ (thanks) named runs well, however- I find that when I kill -HUP named to reload the files, I get "cannot open /etc/named.conf" is this just not observing the chroot? It's funny because I have /etc/named.conf symlink'd to the real file which lives in /var/named/etc/named.conf. I do not quite get it why I can't HUP the nameserver... This is quite an annoying problem. Normally, named is started with: /var/named/named -u bind -g bind -t /var/named I also tried: /var/named/named -c /var/named/etc/named.conf -u bind -g bind -t /var/named and for the hell of it: /var/named/named -c /etc/named.conf -u bind -g bind -t /var/named I only have a problem with a kill -HUP though, other then that it works fine. FYI, /var/named/etc/named.conf is mode 640, owned root:bind. ndc also breaks in a few funny ways, but I can live without it, but named dying on HUP is very annoying. Thanks in advance. Matt -- "If the primates that we came from had known that someday politicians would come out of the...the gene pool, they'd a stayed up in the trees and written evolution off as a bad idea. Hell, I always thought the opposable thumb was overrated." -Sheridan, "A Distant Star" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.9911150526100.50886-100000>