From 306a8ee991a42055365aade54b9c988e5373cef5 Mon Sep 17 00:00:00 2001 From: Eric Sandeen Date: Thu, 30 Apr 2009 10:56:04 -0500 Subject: fix max-pkts option inconsistencies This is for RH bug 498426, btrecord doesn't recognize --max-pkts and --max-packets cmd line options Usage text and some documentation references "--max-pkts" and the man page references "--max-packets" but the getopts code is looking for --max_pkts. I'm not sure if it's best to make the code match the majority of the docs, or fix the docs to match the code? This patch does the former, but I'm not picky if you want to go the other way :) Signed-off-by: Eric Sandeen Signed-off-by: Jens Axboe --- btreplay/btrecord.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'btreplay') diff --git a/btreplay/btrecord.c b/btreplay/btrecord.c index 09329f7..88ab806 100644 --- a/btreplay/btrecord.c +++ b/btreplay/btrecord.c @@ -152,7 +152,7 @@ static struct option l_opts[] = { .val = 'm' }, { - .name = "max_pkts", + .name = "max-pkts", .has_arg = required_argument, .flag = NULL, .val = 'M' -- cgit v1.2.3