r396801 modified the port to pass --disable-debug to configure unless the port's DEBUG option is set. Previous behaviour was that configure would enable debug by default. SYSLOG depends on DEBUG, so now slapd will not log to syslog unless the port is build with the DEBUG option selected. rwsrv04> grep LDAP_SYSLOG work/openldap-2.4.42/servers/slapd/main.c #if defined(LDAP_DEBUG) && defined(LDAP_SYSLOG) #endif /* LDAP_DEBUG && LDAP_SYSLOG */ #if defined(LDAP_DEBUG) && defined(LDAP_SYSLOG) #if defined(LDAP_DEBUG) && defined(LDAP_SYSLOG) #endif /* LDAP_DEBUG && LDAP_SYSLOG */ #if defined(LDAP_DEBUG) && defined(LDAP_SYSLOG) #endif /* LDAP_DEBUG && LDAP_SYSLOG */ Perhaps this outcome is intentional? I would have thought most admin's would want slapd logging at all times. I am logging this bug just in case this was not an intentional side-effect of r396801.
(In reply to John Marshall from comment #0) Disclaimer -- It's not me don't consider this a problem but I didn't find something like "third party to resolve" and the "Rejected" seems to be the closest reason for closing. I'd suggest bringing this up to openldap-technical@openldap.org and we can discuss there. In my _personal_ opinion, this new behavior is desirable as production servers should not log queries in this detail (it's like a database server, you only want to log detailed query information when debugging it) at all. However, I understand that opinion itself may be controversial, because the decision is made at build time, and there may be some system administrators who do not want to debug the server but find the logged information useful (I don't personally, because the directory service is not facing the Internet, and those who bind the server have already logged their login/authentication activities). Since I didn't write the OpenLDAP code myself, I think it's better that we ask the upstream maintainers for their opinion, and the port will follow the upstream decision on this one. Hope this helps and thanks for noticing this.