[bind10-dev] How to have a pleasant conversation with the administrator about life, the universe, and everything, OR The Problem of the Unused SQL Column

[Paul Ebersman]

stephen> Option (b) appears to be the simplest, especially if we were to
stephen> reserve a facility or severity code for such a message.  In a
stephen> number of Unix variants we would get this functionality for
stephen> free: many variants allow you to set up syslog to write a
stephen> message to all (or some) logged on users depending on facility
stephen> and/or severity.  Some variants allow you to route messages to
stephen> named pipe to which you could can attach a program of your
stephen> choice.

syslog is certainly a "standard" among unixi. However, bind9 does its
own logging as one option because so many version of syslog are
performance nightmares.

I think that the model where you syslog just long enough for the bind10
modules to start logging per configuration, then have some choices,
including using syslog, using our own logging, etc.

There are all sorts of things in bind9 I won't miss, but logging options
available in bind9 work pretty well. ;)