Bug 1397288
Summary: | Typo in logconv.pl man page | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Marc Muehlfeld <mmuehlfe> |
Component: | 389-ds-base | Assignee: | mreynolds |
Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | amsharma, mreynolds, nkinder, rmeggins |
Target Milestone: | pre-dev-freeze | ||
Target Release: | 7.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 389-ds-base-1.3.6.1-6.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 21:12:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marc Muehlfeld
2016-11-22 07:54:53 UTC
Upstream ticket: https://pagure.io/389-ds-base/issue/49205 Fixed upstream 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 |