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

[Stephen Morris]

On 19/07/2011 15:21, Shane Kerr wrote:
> All,
> 
> Right now logging defaults to the console, like this:
> 
> 2011-07-19 14:18:10.402 INFO  [b10-xfrin.xfrin] XFRIN_AXFR_TRANSFER_SUCCESS AXFR transfer of zone time-travellers.nl.eu.org. succeeded
> 2011-07-19 14:18:10.403 INFO  [b10-xfrout.xfrout] XFROUT_NOTIFY_COMMAND received command to send notifies for time-travellers.nl.eu.org./IN
> 2011-07-19 14:18:22.348 INFO  [b10-auth.datasrc] DATASRC_QUERY_NO_ZONE no zone containing 'borg.c-l-i.net.' in class 'IN'
> 2011-07-19 14:18:22.348 INFO  [b10-auth.datasrc] DATASRC_QUERY_NO_ZONE no zone containing 'madras.curryboys.net.' in class 'IN'
> 
> I was thinking perhaps the default logging should go to a file or syslog
> instead.

We can change the default quite easily.

> Or maybe we set this up to have errors (and more severe
> messages) go to the console and informational (and more severe) messages
> go to files/syslog?

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.

Stephen