Am So, den 26.03.2006 schrieb Noah um 18:03: > something is still wrong. I made the change in the /etc/named.conf file to > match the exact logfile location and added /var and still have troubles > > # pwd > /etc > # ls -ld named.conf > lrwxrwxrwx 1 root root 32 Mar 25 18:39 named.conf -> > /var/named/chroot/etc/named.conf > # grep namedlog named.conf > file "/var/log/named/namedlog.log" versions 3 size 40m; > > > and from /var/log/messages > > --- snip --- > > Mar 26 08:00:05 protect1 named[28098]: isc_log_open > '/var/log/named/namedlog.log' failed: file not found > > --- snip --- Looks like you are mixing bind and bind-chroot. From above pasted symlink named.conf you are running bind-chroot, for which all content has to be by Fedora default inside /var/named/chroot/. It does not matter if you have a /var/log/named/ location created. The default location for log data with bind-chroot on Fedora Core 4 is /var/named/chroot/var/named/data/. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 18:20:56 up 12 days, 19:08, load average: 0.19, 0.15, 0.10
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
