Hello,
While scanning some systems (usually *nix systems but once in a while
a printer or a windows system), Nmap ends up running for many hours.
Based on client instructions, it seemed that the option "Host Timeout
(ms)" would set an upper limit. However, based on review of the logs, it
appears that Nmap scans go way beyond the limits set. Has anyone had
better luck with constraining Nmap from within a Nessus run?
We have used 1.2.6 and 1.3.4 on Red Hat 7.2 or 7.3 with various
configurations.
Thank you,
Bob
