[bind10-dev] Planning for next sprint - input required

[Jerry Scharf]

Michael,

You are a great set up man.

My comment about whether people are using logging as the tool they have 
to do things that may not be best done with logging was about just this. 
If you are trying to do figure out what happened from a past event, 
logging is the perfect tool. If it is an infrequent event, logging is 
possible but requires you to filter the useful response out of the 
flood. If you are trying to debug why something is working a given way 
in the active server, I think there are better designs than to overload 
logging.

Separating the problems to be solved from the solutions is the key 
starting point.

jerry s

On 11/30/2010 11:31 AM, Michael Graff wrote:
> IMHO, just pick one.  This discussion has gone on now for a very long
> time and there will always be debate here.
>
> What's more important to me anyway is debugging a server or a problem,
> and it doesn't matter much which logging subsystem is chosen for that.
> It's a code style change that changes from "log events as they happen"
> to "make it easy to debug a problem" and I'm never certain simple
> logging will fix that.
>
> --Michael
>
> _______________________________________________
> bind10-dev mailing list
> bind10-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind10-dev