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.

this bug has been verified:

-M, --reportFileMins <CSV output file>
This option creates a CSV report for spreadsheets.

-m, --reportFileSecs <CSV output file>
This option creates a CSV report for spreadsheets.

-B, --bind <ALL | ANONYMOUS | Bind DN >
This generates a report based on either ALL bind dn’s, anonymous binds, or a specific DN.

-D, --data <Location for temporary data files>
DEFAULT -> /tmp
TIP -> If there is not enough RAM, a RAM disk can be used instead:

mkdir /dev/shm/logconv, and use this directory for the "-D" value.


this bug is verified on 389-ds-base 1.2.11.15 build

Should this bug be marked VERIFIED then instead of ASSIGNED?

(In reply to Rich Megginson from comment #3)
> Should this bug be marked VERIFIED then instead of ASSIGNED?

Yes Rich. That is by mistake.

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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html