Re: problem about max_hosts and max_checks settings
Ron Gula <[email protected]>
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Message-ID | <[email protected]> |
Nessus does not use one daemon per plugin. If it did, it would not be that fast. If you had two nessusd processes, one was likely the main nessusd process (waiting for new scan jobs) and the other was doing your scanning within the parameters of your max hosts and checks. If you scanned more targets, you'd get more nessusd processes being forked off, but it's not a 1-target to 1-nessusd ratio. Ron Gula Tenable Network Security 赵永胜 wrote: > I set max_hosts = 15 and max_checks = 20 in the file nessusd.conf, and the same in my nessusrc file, then I started my scan according to the command : > > nessus -c nessusrc -qx localhost 1241 user pwd targets result.xml > > the content of my targets file is 192.168.2.2. > > when I checked the nessus process number via this command : ps aux | grep nessus, I found that there were only > one or two 'nessusd: testing 192.168.2.2 ...' but not 20 such processes at the same time. > > could someone tell why? > thanks in advance. > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus