Even if we set the expirationTime in /var/lib/pki-ca/conf/CS.cfg, the logs do not get deleted after the time elapsed.
By default the value is 0, it seems that by default it will not delete the logs.
log.instance.System.expirationTime=0 log.instance.System.fileName=/var/lib/pki-ca/logs/system
How to reproduce:
Set time in seconds as below : log.instance.System.expirationTime=90 log.instance.System.fileName=/var/lib/pki-ca/logs/system
Actual results:
The logs does not get deleted after the time elapsed
Expected results:
The logs should be deleted.
Per Dogtag 10.3 Triage meeting of 01/06/2016: Dogtag 10.4, priority medium.
Metadata Update from @krajguru: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: UNTRIAGED)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Audit logs are not removed automatically by design. This is easily solved by using a cronjob or similar to clean up old audit logs. Closing as WONTFIX.
Metadata Update from @mharmsen: - Issue close_status updated to: wontfix - Issue set to the milestone: 10.5.0 (was: 10.6) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.1 (was: 10.5.0)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2284
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.