[PATCH] Fix an error message involving --max-retries

[Kris Katterjohn <kjak () ispwest com>]

The attached patch replaces "max-retransmissions" with "max-retries" in
an error message in nmap.cc

It's a diff against 4.20ALPHA6 (but applies cleanly to ALPHA7)

Thanks,
Kris Katterjohn

diff -uprN x/nmap.cc y/nmap.cc
--- x/nmap.cc   2006-09-02 16:50:41.000000000 -0500
+++ y/nmap.cc   2006-09-12 20:05:01.000000000 -0500
@@ -699,7 +699,7 @@ int nmap_main(int argc, char *argv[]) {
       } else if (optcmp(long_options[option_index].name, "max-retries") == 0) {
         pre_max_retries = atoi(optarg);
         if (pre_max_retries < 0)
-          fatal("max-retransmissions must be positive");
+          fatal("max-retries must be positive");
       } else if (optcmp(long_options[option_index].name, "randomize-hosts") == 0
                 || strcmp(long_options[option_index].name, "rH") == 0) {
        o.randomize_hosts = 1;


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org