From e326bc026618a7d8091abce5395794abec61cef9 Mon Sep 17 00:00:00 2001 From: kris Date: Sun, 28 Jan 2007 13:18:32 +0000 Subject: [PATCH] Fix --max-os-tries and --max-rtt-timeout options. There was a typo which caused two optcmp()s to be checking for max-rtt-timeout instead of one for that and one for max-os-tries. Since the first one was supposed to check for max-os-tries, --max-rtt-timeout has been setting max-os-tries. This meant there was no way to set max-rtt-timeout, and --max-os-tries always failed with an error message. --- nmap.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nmap.cc b/nmap.cc index 35c1e71f7..9c8695d2c 100644 --- a/nmap.cc +++ b/nmap.cc @@ -637,7 +637,7 @@ int nmap_main(int argc, char *argv[]) { o.scriptupdatedb = 1; } else #endif - if (optcmp(long_options[option_index].name, "max-rtt-timeout") == 0) { + if (optcmp(long_options[option_index].name, "max-os-tries") == 0) { l = tval2msecs(optarg); if (l < 1 || l > 50) fatal("Bogus --max-os-tries argument specified, must be between 1 and 50 (inclusive)");