Re: slapo accesslog purge in 2.3.19 [auf Viren ÃberprÃft]

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Thursday, November 02, 2006 11:50 AM +0100 Hans Moser 
<hans.moser@ofd-sth.niedersachsen.de> wrote:

> Hi!
>
> I activated overlay accesslog in a 2.3.19 server. Everthing works fine
> (changes are logged) as long as I do not activate logpurge:
>
> line 69 (overlay accesslog)
> line 70 (logdb "ou=log,ou=foo,o=bar,c=de")
>  >>> dnPrettyNormal: <ou=log,ou=foo,o=bar,c=de>
> <<< dnPrettyNormal: <ou=log,ou=foo,o=bar,c=de>, <ou=log,ou=foo,o=bar,c=de>
> line 71 (logops writes)
> line 72 (logpurge 10+00:00 1+00:00)
> /opt/mail//etc/openldap/slapd.conf: line 72: <logpurge> handler exited
> with 1!
> slapd destroy: freeing system resources.
> slapd stopped.
> connections_destroy: nothing to destroy.
>
>
>
> # in slapd.conf
> overlay accesslog
> logdb "ou=log,ou=foo,o=bar,c=de"
> logops writes
> logpurge 10+00:00 1+00:00
>
> This seems not to be related to ITS#4505 or #4595, which occour in
> CHANGES for "accesslog purge" for version >2.3.19.

There were bugs fixed with log purging at some point past 2.3.19.  I'd 
advise running the latest release (2.3.28), since there are numerous other 
bugs fixed since 2.3.19 too.

--Quanah


--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html