We have a setup with a very high number of binds, so running with loglevel 256
floods the log file.
According to
http://www.openldap.org/lists/openldap-software/200205/msg00120.html John
Dalbec wrote a patch for this
for 2.0.21, but AFAICS it was ever submitted.
I would like to have eg. loglevel
Andreas Taschner wrote:
We have a setup with a very high number of binds, so running with loglevel 256
floods the log file.
According to
http://www.openldap.org/lists/openldap-software/200205/msg00120.html John
Dalbec wrote a patch for this
for 2.0.21, but AFAICS it was ever submitted.
I would
On 1/11/07, Pierangelo Masarati <[EMAIL PROTECTED]> wrote:
Andreas Taschner wrote:
> We have a setup with a very high number of binds, so running with loglevel
256 floods the log file.
> According to
http://www.openldap.org/lists/openldap-software/200205/msg00120.html John Dalbec
wrote a patch
On Thursday 11 January 2007 16:37, Pierangelo Masarati wrote:
> Andreas Taschner wrote:
> > We have a setup with a very high number of binds, so running with
> > loglevel 256 floods the log file. According to
> > http://www.openldap.org/lists/openldap-software/200205/msg00120.html John
> > Dalbec w
Ralf Haferkamp wrote:
Is that really possible in OpenLDAP 2.3 from the man-page I only see that you
can configure it in a way that only successful operations are
logged "logsuccess TRUE", but "logsuccess FALSE" will log everything (failed
and successful)
Am I overlooking something?
You're r