In some lib389 tests we use:
<instance>.deleteErrorLogs()
This is done to have a clean error log to check for messages, but for debugging purposes logs are lost.
It would be better to have a method
<instance>.rotateErrorLogs()
Maybe this requires enhancement of DS to allow enforcing of log rotation, or it coul be triggered by temporariliy changing the rotation config
I think this will need to be a feature in the server, because that's really the only part that has the correct access to do the filesystem rotation.
Metadata Update from @firstyear: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.2
Metadata Update from @vashirov: - Issue priority set to: minor - Issue set to the milestone: 1.4.4 (was: 1.4.2)
Metadata Update from @mreynolds: - Issue tagged with: RFE
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3377
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. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.