On 12/11/12 15:23, Ed LaFrance wrote:
I really don't need this kind of logging in the messages log. I can turn
on query logging in the named.conf if I need more detail on named. I
think the simplest thing would just be to have an exclusion in the
syslog config for named. I confess some general ignorance, so perhaps
Don't do that. Instead, configure named to not syslog if you don't want
it to. Maybe log to files from within named, which is quicker.
you know the directive for that?
As per the ARM:
http://www.isc.org/files/arm94_0.html#id2574861
...the defaults are:
"""
Only one logging statement is used to define as many channels and
categories as are wanted. If there is no logging statement, the logging
configuration will be:
logging {
category default { default_syslog; default_debug; };
category unmatched { null; };
};
"""
You can easily change this so that queries aren't logged to syslog. For
example:
logging {
channel query_log { file "logs/query.log"; versions 4; size 10m; };
category queries { query_log; };
category default { default_syslog; default_debug; };
category unmatched { null; };
};
I would recommend tuning this further, as other log categories can
generate a lot of output too. In fact, unless you need to, I would not
use syslog for named at *all* e.g.
logging {
channel query_log { file "logs/query.log"; versions 4; size 10m; };
channel named_log { file "logs/named.log"; versions 4; size 10m; };
category queries { query_log; };
category default { named_log; };
};
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
