Description of problem: The usage message claims that btrecord supports command line option called --max-pkts . The man page claims that btrecord supports command line option called --max-packets . Both of them are rejected by the utility. On the other hand the utility supports command line option called --max_pkts ('-' vs. '_' problem). Version-Release number of selected component (if applicable): blktrace-1.0.0-3.el5 How reproducible: always Steps to Reproduce: # man btrecord | col -b | grep -A 1 -B 1 "max-packets" -M <num> --max-packets=<num> Set maximum number of packets per bunch. The -M option requires # btrecord --max-packets 2>&1 | head -n 2 btrecord: unrecognized option `--max-packets' Usage: btrecord -- version 0.9.3 # btrecord --help 2>&1 | grep "max-pkts" [ -M <pkts> : --max-pkts=<pkts> ] Default: 8 # btrecord --max-pkts 2>&1 | head -n 2 btrecord: unrecognized option `--max-pkts' Usage: btrecord -- version 0.9.3 Actual results: inconsistency between man page, usage message and the utility Expected results: modified man page and modified usage message Additional info:
Thanks, sent a patch upstream to make things consistent on "--max-pkts" though maybe it'd be better to make the docs match the existing "--max_pkts" that the code accepts.... we'll see which one Jens prefers. -Eric
http://git.kernel.dk/?p=blktrace.git;a=commitdiff;h=306a8ee991a42055365aade54b9c988e5373cef5
Committed & built in blktrace-1.0.0-6.el5
Patch committed by upstream. Qa acked for 5.4.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1284.html