Hello, Andrey,
I tried to reproduce the problem with these config parameters, but I
could not.
nsslapd-accesslog-logging-enabled: on
nsslapd-accesslog-maxlogsperdir: 10
nsslapd-accesslog-mode: 600
nsslapd-accesslog-maxlogsize: 10
nsslapd-accesslog-logrotationtime: 1
nsslapd-accesslog-logrotationtimeunit: day
nsslapd-accesslog-logrotationsync-enabled: on
nsslapd-accesslog-logrotationsynchour: 10
nsslapd-accesslog-logrotationsyncmin: 40
nsslapd-accesslog: /var/log/redhat-ds/slapd-laputa/access
It rotated the access log at 10:40, but it did not remove my
older/oldest log access.20070810-173005:
total 11788
-rw------- 1 nobody nobody 8570855 Aug 13 10:52 access
-rw------- 1 nobody root 108003 Aug 10 17:33 access.20070810-173005
-rw------- 1 nobody nobody 1845874 Aug 13 10:33 access.20070813-103043
-rw------- 1 nobody nobody 1453655 Aug 13 10:40
access.20070813-103824 <=== rotated at 10:40
-rw------- 1 nobody root 377 Aug 13 10:40 access.rotationinfo
-rw------- 1 nobody root 0 Aug 10 17:30 audit
-rw------- 1 nobody root 63 Aug 10 17:30 audit.rotationinfo
-rw------- 1 nobody root 5878 Aug 13 10:38 errors
-rw------- 1 nobody root 63 Aug 10 17:30 errors.rotationinfo
Do you happen to have any other advice I could test on?
Thanks,
--noriko
Andrey Ivanov wrote:
> I don't know whether it's a feature or a bug :) I have the following
> configuration for the log management :
>
> nsslapd-accesslog-logging-enabled: on
> nsslapd-accesslog-maxlogsperdir: 365
> nsslapd-accesslog-mode: 600
> nsslapd-accesslog-maxlogsize: 120
> nsslapd-accesslog-logrotationtime: 1
> nsslapd-accesslog-logrotationtimeunit: day
> nsslapd-accesslog-logrotationsync-enabled: on
> nsslapd-accesslog-logrotationsynchour: 0
> nsslapd-accesslog-logrotationsyncmin: 0
> nsslapd-accesslog: /Logs/Ldap/access
>
> nsslapd-accesslog-logmaxdiskspace: 50000
> nsslapd-accesslog-logexpirationtime: 12
> nsslapd-accesslog-logexpirationtimeunit: month
> nsslapd-accesslog-logminfreediskspace: 2000
>
> It means, essentially, that the logs are rotated once a day at
> midnight (or if the file is larger than 120Mb) and that i keep them
> for 1 year.
>
> If i don't set the log rotation time (logrotationsynchour and
> logrotationsyncmin) everything is ok, the logs are rotated once a day
> and then they are kept for the necessary time period.
> However when i set this rotation time the server deletes ALL the logs
> but the current and the last one. That is, after each rotation i have
> the current log (the file 'access') and the previous one (yesterday's
> log, like access.20070811-000030). All the oher log files are deleted.
>
> So if i want to keep the logs i need to copy them to a different place
> by a cron script which is not very elegant :)
>
> So, is it a bug or a feature? :)
>
> Andrey Ivanov
> tel +33-(0)1-69-33-99-24
> fax +33-(0)1-69-33-99-55
>
> Direction des Systemes d'Information
> Ecole Polytechnique
> 91128 Palaiseau CEDEX
> France
>
> ----------------------------------------------------------------
> This message was sent using X-WebMail
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20070813/b7e7f634/attachment.bin
