Each time the installer script is executed it will generate the following log file:
/var/log/pki/pki-<subsystem>-<script>.<timestamp>.log
There is no mechanism to purge the log files automatically, so the log files will accumulate and waste disk space. This could be a problem, especially on test machines.
A possible solution is to use rotating log files, so the number of files and their size will be limited:
/var/log/pki/<script>.log /var/log/pki/<script>.log.1 ... /var/log/pki/<script>.log.10
Each log message has a timestamp, so it should be possible to distinguish one script execution from another.
Additionally, the logging configuration should be stored in a file such as /etc/pki/logging.conf so it can be customized.
Metadata Update from @edewata: - Issue set to the milestone: 10.4
Per CS/DS meeting of 04/24/2017: FUTURE - critical
Metadata Update from @mharmsen: - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 10.4)
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/1082
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.