All,
On Friday, 2013-01-18 10:01:49 +,
"Niall O'Reilly" wrote:
>
> On 18 Jan 2013, at 06:27, Jan-Piet Mens wrote:
>
> >> Could "CLI utility" be man(1) and info(1)? :-)
> >
> > It could, yes, but `b10-msg NNN` isn't going to break BIND 10's
> > development budget (I hope),
>
> +1
>
On 17 Jan 2013, at 18:33, Jeremy C. Reed wrote:
> BIND 9 by default has logging using syslog, using its daemon facility,
> and logging of info or higher.
>
> Is using syslog a sane default for new installations or when using
> official vendor packages with their startup scripts?
Defin
On 18 Jan 2013, at 06:27, Jan-Piet Mens wrote:
>> Could "CLI utility" be man(1) and info(1)? :-)
>
> It could, yes, but `b10-msg NNN` isn't going to break BIND 10's
> development budget (I hope),
+1
> and I feel it to be more practical than
> scrolling through a man page with 900+ err
On 17 Jan 2013, at 20:58, Mike Hoskins (michoski) wrote:
> Syslog as the default is perfectly fine with us.
Please keep that as the default, following the
principle of least astonishment.
> I do also use the rotated file method a few places, so hoping that doesn't
> disappear.
> Could "CLI utility" be man(1) and info(1)? :-)
It could, yes, but `b10-msg NNN` isn't going to break BIND 10's
development budget (I hope), and I feel it to be more practical than
scrolling through a man page with 900+ error-messages in it. ;)
But even a simple text file installed on the serve
-Original Message-
From: Alan Batie
Date: Thursday, January 17, 2013 1:52 PM
To: "bind-users@lists.isc.org"
Subject: Re: what do you use for logging?
>On 1/17/13 10:48 AM, Jan-Piet Mens wrote:
>
>>> By the way, all of the BIND10 logging
>>> me
On 1/17/13 10:48 AM, Jan-Piet Mens wrote:
>> By the way, all of the BIND10 logging
>> messages are unique and we provide a paragraph or more documentation for
>> each of its 933 possible log identifiers!)
>
> I haven't checked whether you have that, but that screams for a CLI
> utility to show
> Is using syslog a sane default for new installations or when using
> official vendor packages with their startup scripts?
I for one would not want to miss BIND9's logging to auto-rotated files:
file "/var/named/log/named.log" versions 10 size 5m;
Other than that, I'd say logging via
BIND 9 by default has logging using syslog, using its daemon facility,
and logging of info or higher.
Is using syslog a sane default for new installations or when using
official vendor packages with their startup scripts?
Do any packagers provide a configuration with different-than-default
log
9 matches
Mail list logo