Saludos Lorenzo y gracias de antemano.
Efectivamente esa separació permite dividir por "evento" ... Pero por dominio o
zona?
Sigo leyendo.
José Gregorio.
Enviado desde mi dispositivo movil BlackBerry® de Digitel.
-----Original Message-----
From: Lorenzo Ortega <lorenzo.ort...@freebyte.es>
Date: Wed, 17 Nov 2010 14:13:54
To: Camaleón<noela...@gmail.com>
Cc: <debian-user-spanish@lists.debian.org>
Subject: Re: Logs de BIND separados.
puedes disgregarlos así, en el named.conf.
logging {
channel default_file { file "var/log/default.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel general_file { file "var/log/general.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel database_file { file "var/log/database.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel security_file { file "var/log/security.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel config_file { file "var/log/config.log" versions 3 size 50m;
severity dynamic; print-time yes; };
channel resolver_file { file "var/log/resolver.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel xfer-in_file { file "var/log/xfer-in.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel xfer-out_file { file "var/log/xfer-out.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel notify_file { file "var/log/notify.log" versions 3 size 50m;
severity dynamic; print-time yes; };
channel client_file { file "var/log/client.log" versions 3 size 50m;
severity dynamic; print-time yes; };
channel unmatched_file { file "var/log/unmatched.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel queries_file { file "var/log/queries.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel network_file { file "var/log/network.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel update_file { file "var/log/update.log" versions 3 size 50m;
severity dynamic; print-time yes; };
channel dispatch_file { file "var/log/dispatch.log" versions 3 size
50m; severity dynamic; print-time yes; };
channel dnssec_file { file "var/log/dnssec.log" versions 3 size 50m;
severity dynamic; print-time yes; };
channel lame-servers_file { file "var/log/lame-servers.log" versions
3 size 50m; severity dynamic; print-time yes; };
category default { default_file; };
category general { general_file; };
category database { database_file; };
category security { security_file; };
category config { config_file; };
category resolver { resolver_file; };
category xfer-in { xfer-in_file; };
category xfer-out { xfer-out_file; };
category notify { notify_file; };
category client { client_file; };
category unmatched { unmatched_file; };
category queries { queries_file; };
category network { network_file; };
category update { update_file; };
category dispatch { dispatch_file; };
category dnssec { dnssec_file; };
category lame-servers { lame-servers_file; };
};
El 17/11/10 14:04, Camaleón escribió:
> El Tue, 16 Nov 2010 23:30:55 -0800, Jose Diaz escribió:
>
>
>> Quería saber si a alguien se le ha presentado alguna vez la necesidad de
>> mantener logs separados para cada uno de los dominios que administra un
>> BIND9.
>>
> (...)
>
> Si al final no encuentras nada para poder configurar los registros por
> separado directamente desde Bind9, lo que también podrías hacer es
> mantener la configuración actual (bind9 los envía al "syslog") y utilizar
> los filtros de "rsyslog" para clasificarlos.
>
> Saludos,
>
>
--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ce3d512.9050...@freebyte.es
