[Date Prev][Date Next]
Re: Logging should be more centralized (ITS#524)
At 04:11 PM 5/3/00 GMT, email@example.com wrote:
>On Wed, May 03, 2000 at 03:57:08PM +0000, firstname.lastname@example.org wrote:
>> Full_Name: Stan Bubrouski
>> Version: 1.2.9
>> OS: linux 2.3.99-pre5
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (22.214.171.124)
>> Basically at the present time I find it annoying to setup logging for each of
>> the components of the OpenLDAP packages because logging isn't any way I can see
>> centralized. For instance some things log to messages others log to local3 or
>> local4 etc... it's hard to keep track of and might be better accomplished using
>> some sort of shared logging mechanism within the OpenLDAP programs that would
>> still utulize syslog, but at the same time filter things out to the proper
>> place. This isn't a bug so I'd just throw this in the enhancements section or
>> something, if you think it's a feasable I can work out some patches to make it a
>> go. If you don't think it it's necessary or it's already being done in the
>> development version let me know, I think people might find it much more useful,
>> as I'm noticing many people's systems aren't even configured to use those
>> particular logging channels (local*.*).
>I'm not sure if the LDAPv3 spec even has some implementation for this,
LDAP is a protocol spec, not an application spec.
>it would be nice if libldap had a log wrapper just for this (atleast for
>anything LDAP related). Then it could be configured in ldap.conf (global
>only, not in the .ldaprc for each user).
This is the idea behind ber_set_option(NULL, LBER_OPT_LOG_PRINT_FN, ...).
This is designed to allow applications to install their own log
handlers. We'll like only support two handlers, syslog (or
equiv) for servers and stderr (or equiv) for tools.