On 2/3/17 8:01 AM, Mukund Sivaraman wrote:
> We have the debug log level, but consider the case when an operator has > a non-deterministic or rare crash that isn't reproducible because the > operator has no information about what caused it. All we have is the > config, log that was already generated before the crash and perhaps a > backtrace and core to deduce the steps leading to the crash. It's not > possible to re-run that scenario with debug logging. > > I'll create a ticket to put the client pointer at the end if that'll > help, but note that the syntax in 9.10 was not consistent either. 9.10 > would log the client pointer when the client object didn't have a valid > peer. Adding code to allow enabling or disabling this output on the fly would work MUCH better (as an example, see "rndc querylog"/ options "querylog [on | off ]"). Adding a "well, we needed this one time" value to the middle of a long-standardized log file does no customer any good and inconveniences everyone. You own the code and can do whatever you want to, but I'd recommend making the default log message what it was prior to 9.10 and adding additional fields via pre-configuration and "rndc". AlanC
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
