The developer of some software we use has come up with this and it
appears to work:
logging{
channel error_log {
file "/var/log/bind.log" versions 3 size 5m;
severity error;
print-time yes;
print-severity yes;
print-category yes;
};
category default{
error_log;
};
};
On 11/12/2012 8:49 AM, David Forrest wrote:
On Mon, 12 Nov 2012, Ed LaFrance wrote:
Hello Alan -
Of course you are right, my bad.
Here's the entirety of my named.conf - there's nothing pertaining to
logging in here, so I guess that means that 'log everything' is the
default. I would only want to log critical named errors, so if anyone
has syntax they have my gratitude:
No, you just get the defaults as described in the ARM 6.2.10
"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; };
};"
The rest of 6.2.10 shows the syntax and provides the ability to "roll"
the logs much as (r)syslogd.conf does for those that syslog gets. None
of my named logs go to syslog as I do have a logging statement of my
choices.
Dave
--
(800) 362-7579 ext 1
+-------------------------------------------------------+
+ Colocation Dedicated Servers IPv4 & IPv6 Transit +
+-------------------------------------------------------+
Connex Internet Services, Inc. direct: (916) 265-1568
11230 Gold Express Dr #310-313 fax: (916) 880-5663
Gold River, CA 95670 http://connexinternet.com
+-------------------------------------------------------+
_______________________________________________
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
