[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: NT log output

The default ber_pvt_log_print function ber_error_print prints
unconditionally to stderr. We ran across this problem too and added a
function ber_error_file(FILE *f) to override the default output stream.
I added invocations of this function in liblutil/debug.c lutil_debug_file()
and lutil_debug() so that our logs would all dump into the same place. It's
been a long time since I've synced up our source tree with the main
repository but I can provide patches for this if desired.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc

> -----Original Message-----
> From: owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Andrew Davison
> Sent: Tuesday, March 14, 2000 6:08 PM
> To: openldap-devel@OpenLDAP.org
> Subject: Re: Fixed. [Q] 2.0-devel fails when enabling cache in client
> No, in the NT build at least, even if you completely disable all debugging
> and use the 'release' config, you still get the BER dumps. It's most
> annoying.
> ----- Original Message -----
> From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
> To: "Adrian Pavlykevych" <pam@polynet.lviv.ua>
> Cc: <openldap-devel@OpenLDAP.org>
> Sent: Wednesday, March 15, 2000 8:56 AM
> Subject: Re: Fixed. [Q] 2.0-devel fails when enabling cache in client
> > >Thanks, it seems to work properly now.
> > >BTW, how can I turn of theese "ber_dump"?
> >
> > You must have some BER logging/debugging enabled.
> >
> > >I haven't set LDAP_DEBUG, but  still
> > >get them.
> >
> > LDAP_DEBUG is enabled by default, try --disable-debug... but you'll lose
> > all debugging.
> >
> > > Should I comment them out of code, or is there some more gentle way?
> >
> > If you are getting ber_dump, you must have BER debugging enabled...
> >