Re: Logging by default

From: Daniel Black <daniel.subs_at_internode.on.net>
Date: Fri, 22 Feb 2013 12:32:57 +1100

On 22/02/13 05:48, Murray S. Kucherawy wrote:
> Based on an offlist conversation:
>
> Should opendkim's "Syslog" setting default to "true"?

yes.

> It's the opposite right now and has been since the beginning. The
> common practice I've had for years now is to be very vocal about errors,
> and refuse to start up, if any problem impeding normal operation can be
> detected. Once started, however, standard output/error are no longer
> available, so you find some way to continue operating (or restarting) at
> all costs, and be as minimally disruptive of the environment as possible.
>
> Daemons on busy machines can log quite a bit, meaning useful data from
> other daemons can be lost in the noise.

There's usually plenty of space and grep.

> We can't make any assumptions
> about which syslog facility should be used, so the whole thing is off by
> default, forcing operators to configure syslogging before it actually
> does anything.

logs don't get looked at until needed. having info there is always more
useful.
Received on Fri Feb 22 2013 - 01:33:09 PST