[bind10-dev] Default logging to file/syslog instead of console?

[Stephen Morris]

On 20/07/2011 12:00, Shane Kerr wrote:
> Stephen,
> : 
> Question 1: syslog or files?
> 
> My personal preference is log files. I've had a few problems throughout
> the years with syslog, so you may need to disregard this opinion. :)

The problem then is "what is the default file"?  At least with syslog,
the output is to a known place


> Question 2: single log file or several?
> : 
> One possible split might be:
> 
>      1. "generic" BIND 10 logging
>      2. logging for zone maintenance (xfrin/xfrout/zonemgr and perhaps
>         notify messages, and probably future DNSSEC automatic signers)
>      3. auth
>      4. resolver
>      5. DHCPv4
>      6. DHCPv6

If we are proposing a more complicated routing of messages than
"everything to syslog", the best way to provide defaults would be to
supply a default b10-config.db as part of the installation with these
pre-set (although we would have to be careful not to overwrite it during
upgrades).


>> At the moment, although you can attach multiple destinations to a
>> particular logger, you can only associate it with one severity.
>>
>> However, I think that the underlying log4cplus supports the idea of
>> associating a severity with a logger's destination (as well as
>> associating a severity with a logger), so this capability should not be
>> too hard to add.
> 
> Okay, then probably we don't need to worry about it for now. However in
> Y4 we'll need this to support conversion from BIND 9 logging
> configurations.

Unless we want to add the capability now just to say that we've
completed logging and have no loose ends to tie up.

Stephen