Date: Thu, 6 Sep 2001 18:06:33 -0400 From: "John Straiton" <jsmailing@clickcom.com> To: "Andrew Eross" <eross_a@chasma.net>, <questions@freebsd.org> Subject: RE: named chroot trouble Message-ID: <PHEMIEFOLOKALAMFPIPCEEFGCBAA.jsmailing@clickcom.com> In-Reply-To: <008101c1371c$8fb57390$8e45b184@eross>
next in thread | previous in thread | raw e-mail | index | archive | help
Once chrooted, named can no longer write to syslog like it used to because it can not get to /dev/log (outside the chroot). You have to tell syslogd to place a pointer within the chroot that named can write to. If your chroot is in /etc/namedb/ then you need to mkdir /etc/namedb/dev then add syslogd_flags="-l /etc/namedb/dev/log" to your rc.conf restart syslogd with those flags and you'll find that there's now a /etc/namedb/dev/log filehandle there. named will write to this and work fine. Chrooting BIND9: http://profile.sh/bsdwiki/index.php?Setting%20up%20secure%20DNS%20servers%20 with%20BIND%20under%20FreeBSD Chrooting BIND8: http://www.psionic.com/papers/dns/dns-openbsd John Straiton -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Andrew Eross Sent: Thursday, September 06, 2001 5:41 PM To: questions@freebsd.org Subject: named chroot trouble Hi, I run named chroot'd on my machine, but I noticed that since it runs chroot'd it no longer reports to syslog ... Is there anything that I can do about this? Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PHEMIEFOLOKALAMFPIPCEEFGCBAA.jsmailing>