Re: [patch] expected behaviour of loglevel - revised patch
norbert at linuxnetworks.de
Sat Nov 8 18:04:28 CET 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 08 November 2003 16:12, you wrote:
> > Yes, the Logger.operator<<() is very often called. I've already
> > thought about using Logger.log() directly. Is there a better way
> > or is the only real option to remove the debugging output?
> Use a DLOG like construct for stuff that is unimportant to most
> people, it gets compiled out. Or add something more dynamic that
> checks a variable before evaluating a line if the loglevel is too
Ok, I reverted back to DLOG() for both debugging lines. The other
option is not very appealing to me up to now.
The attached diff obsoletes the previous two ldapbackend patches. It
- - SRV record support (Matt Dainty)
- - TLS support (Matt Dainty)
- - DoS fix for invalid MX records
- - Fix for crash in constructor in special error condition
- - Ldap reference support
- - Better logging
Support for different syslog levels would be nice, but after removing
debug output by DLOG() it is not urgent any more. Perhaps later ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7245 bytes
Desc: not available
Url : http://mailman.powerdns.com/pipermail/pdns-dev/attachments/20031108/3d785470/ldapbackend_new-0001.bin
More information about the Pdns-dev