On Wednesday 08 August 2001 09:25 am, Mike Burger wrote:
> Steve Snyder <[EMAIL PROTECTED]> said:
> > Has anyone gotten BIND to write to log to file /var/named.log?
> >
> > Seawolf seems to expect BIND logging to that file (see file
> > /etc/logrotate.d/named), but permissions prevent that.  BIND is running
> > as non-root (uid=named, gid=named) so it is unable to write to the
> > /var/log subdirectory.
> >
> > Thanks.
>
> I have the following near the top of my named.conf file...just below the
> "Options" section.  Through it, I have various logs for different parts
> of the named logging.
>
> You're welcome to use it as you see fit:
>
> logging {
>         channel my_syslog { file "/var/log/named/named.log" versions 5;
>                                 severity info;
>                                 print-category yes;
>                                 print-time yes;
>                                 };
>         channel my_lame { file "/var/log/named/lame.log" versions 5;
>                                 severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>         channel my_xfer { file "/var/log/named/xfer.log" versions 5;
>                                 severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>         channel my_update { file "/var/log/named/named.update" versions
> 5; severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>         channel my_db     { file "/var/log/named/db.log" versions 5;
>                                 severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>          channel my_query  { file "/var/log/named/query.log" versions 2;
>                                 severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>         channel my_security { file "/var/log/named/security.log" versions
> 99; severity info;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>         channel my_debug { file "/var/log/named/named.debug" versions 20;
>                                 severity dynamic;
>                                 print-category yes;
>                                 print-time yes;
> //                              size 50M;
>                                 };
>
>
>         category security       { my_security; };
>         category default        { my_syslog; };
>         category queries        { my_query; };
>         category lame-servers   { my_lame; };
>         category update         { my_update; };
>         category db             { my_db; };
>         category xfer-in        { my_xfer; };
>         category xfer-out       { my_xfer; };
>         category packet         { null; };
>         category eventlib       { my_syslog; };
>
>
> };

So do you leave the logrotate named config unused and rely on BIND to 
rotate the logs for you?  How does it know the frequency with which to 
rotate them?

Thanks.



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to