On Jan 2, 2006, at 21:57, Paul Melson wrote:
I took Nessus 3.0.0-fc4 for a test drive today and had an odd
result. The
machine in question is a stock, fully updated FC4 install on a Dell
laptop.
Everything went smoothly until I actually launched my first scan. The
nessusd process properly spawned nmap to begin the portscan and then
immediately pegged the CPU. Here's the last few lines of
nessusd.messages:
[...]
While typing this message, nmap completed successfully, at which point
nessusd went back to a normal level of CPU usage and the scan
completed
successfully. This is liveable, but I'm wondering if there's a fix
or if
this information is useful to the Nessus team.
This will be fixed in 3.0.1 -- thanks !
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
