Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
LOGCONV.PL(1) General Commands Manual LOGCONV.PL(1)
NAME
logconv.pl - analyzes Directory Server access log files
[root@ibm-x3250m4-02 ~]# rpm -qa | grep 389
389-ds-base-1.3.6.1-6.el7.x86_64
389-ds-base-libs-1.3.6.1-6.el7.x86_64
man logconv.pl
==================
SYNOPSIS
logconv.pl [-h] [-d <rootDN>] [-s <size limit>] [-v] [-V] [-S <start time>] [-E <end time>] [-T <min etime>] [-efcibaltnxgjuU] [ access log
... ... ]
DESCRIPTION
Analyzes Directory Server access log files for specific information defined on the command line
OPTIONS
A summary of options is included below:
-h, --help
help/usage
-d, --rootDN <Directory Managers DN>
DEFAULT -> cn=directory manager
-D, --data <Location for temporary data files>
DEFAULT -> /tmp
TIP -> If there is enough RAM, a RAM disk can be used instead:
mkdir /dev/shm/logconv, and use this directory for the "-D" value.
Hence VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2086