Redirect named logs using the "logging" feature in your named.conf file.

For example, I have, in mine:

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; };
 
 
};

You can, of course, omit anything preceded by a //, if you like...they're 
commented out, obvously.  Most of them are file size parameters, but I've 
enough space in my /var file system that it's not an issue, and the logs 
get rotated on a regular basis, anyhow.

The rest should be fairly self explanatory.

On Mon, 6 Jan 2003, Ashley M. Kirchner wrote:

> 
>     How can I suppress these bind-9 messages in syslog:
> 
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 64.29.158.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.45.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 64.29.158.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.46.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.45.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.46.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 64.29.158.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.45.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 64.29.158.39#53
> named[25867]: lame server resolving 'majortravel.com' (in 
> 'majortravel.com'?): 216.251.46.39#53
> 
> 

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to