Date: Sat, 30 May 2009 15:51:09 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: Prokofyev Vladislav <v.prokofyev@gmail.com> Subject: Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found Message-ID: <200905301551.09796.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <46dcef4e0905300550j3e19424bs689a384bb4f97c19@mail.gmail.com> References: <46dcef4e0905300550j3e19424bs689a384bb4f97c19@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote:
> Bind9 started in chroot:
>
> root 788 0.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
> /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
> bind 30792 0.0 1.2 16212 12864 ?? Is 4:10PM 0:00.23
> /usr/sbin/named -t /var/named -u bind
>
>
> Configuration of logging channels from named.conf:
>
> logging
> {
>
> channel "xfer"
> {
>
> file "/var/named/var/log/xfer.log" versions 3 size
> 10m;
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905301551.09796.mel.flynn%2Bfbsd.questions>