Re: named listening on LAN
- From: Zbigniew Szalbot <zbigniew@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Jul 2007 12:54:53 +0200
Hello,
This is interesting. I tried adding this to named.conf (adapted from man
named.conf)
/* logging {
channel namedlog {
file /var/log/named/nlog;
severity info;
print-time yes;
print-severity yes;
print-category yes;
};
category default { namedlog; ... };
};
*/
Of course the above was not commented in the configuration file. But when
starting named, it did not want to work. I had to comment the logging
facility and then I was able to get named to work again.
I changed the above to
logging{
channel simple_log {
file "/var/log/named/nlog" versions 3 size 5m;
severity info;
print-time yes;
print-severity yes;
print-category yes;
};
category default{
simple_log;
};
};
Now bind does not die but but it cannot find the log file:
logging channel 'simple_log' file '/var/log/named/nlog': file not found
ls /var/log/named/*
/var/log/named/nlog
Why would named not be able to find the log when it is there? The nlog file
is owned by user bind and grup bind.
Thank you in advance for any suggestion you may have!
Zbigniew Szalbot
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- named listening on LAN
- From: CK
- named listening on LAN
- Prev by Date: Re: finding the USB drive name, mounting and formatting
- Next by Date: Mail on freebsd.org
- Previous by thread: Re: named listening on LAN
- Next by thread: named listening on LAN
- Index(es):
Relevant Pages
|
|
