Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1397288
Description of problem: The logconv.pl(1) man page recommends to use a RAM disk for the -D parameter, if there is _NOT_ enough RAM, what makes no sense. Version-Release number of selected component (if applicable): DS 10.1: 389-ds-base-1.3.5.10-11.el7.x86_64 DS: 9.1: 389-ds-base-1.2.11.15-84.el6_8.x86_64 Steps to Reproduce: 1. Open the logconv.pl(1) man page Actual results: > -D, --data <Location for temporary data files> > DEFAULT -> /tmp > TIP -> If there is not enough RAM, a RAM disk can be used instead: Expected results: > TIP -> If there is enough RAM... Additional info: This is wrong in the DS 9.1 and 10.1.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1397288
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to new - Custom field type adjusted to defect
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: new)
Looks good!
Metadata Update from @nhosoi: - Custom field reviewstatus adjusted to ack (was: review)
fa5e2d0..5c19ef0 master -> master
d2fba36..a66484c 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2264
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 (was: fixed)