Costas Magkos said on Fri, Mar 26, 2004 at 07:53:49PM +0200: > Hi all, > > I have set up bind9 in a chroot'ed enviroment. I've just found out that > I should have added SYSLOGD="-a /var/lib/bind9/dev/log" in > /etc/init.d/sysklogd in order for bind to be able to log messages after > it starts up. Since bind was logging just fine without this addition in > sysklogd startup script, I' m beggining to have doubts about the > fuctionality of the chroot. > > Is there a way to test whether a chroot works? Does anyone know if the > above syslog option is really needed? According to the man page of > syslog it is needed. Apparently, bind9 doesn't require that syslog listen inside of the chroot if you are using the bind9 -t option for chrooting. It opens the syslog socket, and then chroots, which means it can still write to the socket. M
Attachment:
pgpyPchRhlPXz.pgp
Description: PGP signature