libraries like libldap, libber, libsasl do error and debug logging, but it is not available in the DS logs.
There is a mechanism to provide a logging function and define debug levels for these libs and get the messages logged in the DS error log.
attachment 0001-Enable-logging-of-error-messages-from-the-openldap-c.patch
the attached patch just shows how it can be doen for libldap and libber, to make it a real patch it has to be determined where and when the debug function and level is set/reset and how to configure it
Hi Ludwig,
Could you please push your patch to the master branch?
If you are leaning toward not to include in the next release, is it ok to push it to 1.3.6?
Just in case you missed my comment above (#comment:5), I'll let you own this ticket... ;)
Metadata Update from @lkrispen: - Issue assigned to lkrispen - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)
Could this be used in LMDB?
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.5 (was: 1.4 backlog) - Issue tagged with: RFE, lmdb
IIRC lmdb doesn't offer any logging or debugging interface, so this isn't really relevant to LMDB .... it would have to come from our backend code wrapping and interpreting any result codes.
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1795
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.