FreeBSD 7.0-RELEASE-p12 bind9 log files not found

2009-05-30 Thread Prokofyev Vladislav
Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10

Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found

2009-05-30 Thread Mel Flynn
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote: Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23

Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found

2009-05-30 Thread Michael Powell
Prokofyev Vladislav wrote: Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004

Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found

2009-05-30 Thread Prokofyev Vladislav
named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike After adding these options on my system, named didn't start at boot. Manully attempt to start it via '/etc/rc.d/named start' brought to the following error: /etc/rc.d/named: WARNING: run_rc_command: cannot

Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found

2009-05-30 Thread Mel Flynn
On Saturday 30 May 2009 17:01:17 Prokofyev Vladislav wrote: The named running chrooted has no clue about /var/named. You can either use ducttape: cd /var/named/var sudo ln -s .. named or just strip /var/named from your config file, hence use /var/log/xfer.log. -- Mel This