Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1451657
Description of problem: -v option is not working for db2ldif.pl Version-Release number of selected component (if applicable): 389-ds-base-1.3.6.1-13.el7.x86_64 How reproducible: Always Steps to Reproduce: [0 root@qeos-41 /]# db2ldif.pl -v -n userRoot -a "/export/backup/" ERROR - Unknown option: -v Usage: db2ldif.pl [-v] [-Z serverID] [-D rootdn] { -w password | -w - | -j pwfilename } [-P protocol] {-n backendname}* | {-s include}* [{-x exclude}*] [-h] [-a filename] [-m] [-M] [-r] [-u] [-C] [-N] [-U] [-E] [-1] [-a filename] Actual results: ERROR - Unknown option: -v Expected results: It should give output in verbose mode.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1451657
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Ticket-49261-Fix-script-usage-and-man-pages.patch" src="/389-ds-base/issue/raw/files/430ca3f35c525aa5d238b4d7ca1de89bd725ce993ecdf9ff15730247fbfb3a69-0001-Ticket-49261-Fix-script-usage-and-man-pages.patch" />
Metadata Update from @mreynolds: - Custom field type adjusted to defect
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review
The patch looks good to me. Ack
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to ack (was: review)
1947503..d63e4cc 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
3bc42bf..b1474a5 master -> master
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: ack) - 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/2320
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)
Login to comment on this ticket.