I would assume it's using udp/tcp socket to the loopback interface instead of the file.
-----Original Message----- From: bind-users-bounces+mhuff=ox....@lists.isc.org [mailto:bind-users-bounces+mhuff=ox....@lists.isc.org] On Behalf Of Rick Dicaire Sent: Thursday, February 18, 2010 4:17 PM To: Bind Users Mailing List Subject: linux chroot reqs changed? Hi folks...after a little experimentation today I've discovered certain files are no longer used in a linux chroot. Linux kernel versions 2.6.2x. Bind versions tested were 9.6.1-P3 and 9.7.0, both compiled from src (not distro pkgs), and started with: /usr/sbin/named -t /var/named -u username Used to be you needed to have (r)syslogd add a listening socket to $CHROOT/dev, have $CHROOT/dev/null, and $CHROOT/dev/random. I removed $CHROOT/dev/null, disabled the extra syslogd socket for $CHROOT/dev/log. Using lsof, it now seems only $CHROOT/dev/random is opened by named, /dev/null is opened. named still logs to syslog, and I can't figure out how syslog is accessed, is it via /dev/log (I don't see it opened by named)? Thanks -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
