Hello,
yes I was asking for the log levels of the command-line tools like ldapsearch. Thanks for your answers.
This doc helps ( https://www.openldap.org/doc/admin24/runningslapd.html ) but is not completely right, as levels 4 and 8 don't do anything special.
I will rely on the this doc for my tests, thanks again.
D.L.
Le lun. 22 juil. 2019 à 16:14, Quanah Gibson-Mount quanah@symas.com a écrit :
--On Monday, July 22, 2019 10:56 AM -0400 Brian Reichert reichert@numachi.com wrote:
I think that the OpenLDAP server and client share debug flags. I may be wrong on this.
This is correct. It's trivial to grep the source and confirm this as well.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Tuesday, July 23, 2019 2:58 PM +0200 danielle lampert danielle55.lampert@gmail.com wrote:
This doc helps ( https://www.openldap.org/doc/admin24/runningslapd.html ) but is not completely right, as levels 4 and 8 don't do anything special.
I will rely on the this doc for my tests, thanks again.
Again, the source code answers all these questions. From that, it is trivial to see that the debug levels used in libldap are:
LDAP_DEBUG_ANY LDAP_DEBUG_TRACE (1) LDAP_DEBUG_ARGS (4) LDAP_DEBUG_CONNS (8) LDAP_DEBUG_BER (16) LDAP_DEBUG_PARSE (2048)
Whether or not you will get anything from some of the debug levels again depends on what the man page clearly notes:
"must be compiled with LDAP_DEBUG defined for this option to have any effect."
For example, LDAP_DEBUG_CONNS is only used one time in libldap, and is wrapped with:
#ifdef LDAP_DEBUG Debug( LDAP_DEBUG_CONNS, "ber_get_next failed.\n", 0, 0, 0 ); #endif
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
danielle lampert -
Quanah Gibson-Mount