question on sockets

I have been running some Nessus scans against two Sun boxes. Nothing
fancy, I am using the latest Nessus running on Slackware 10.0. However
the scans seem to be taking an incredibly long time for these two
boxes. I keep getting the following message in my nessusd.dump:

sh: line 1: sysctl: command not found
sh: line 1: sysctl: command not found
sh: line 1: sysctl: command not found
sh: line 1: sysctl: command not found
socket: Too many open files
socket: Too many open files
socket: Too many open files
socket: Too many open files
No more open socket?
No more open socket?


Not sure what kind of sysctl call Nessus is trying to make, but then I
get the too many open files and no more open socket messages. I am
having to scan the boxes through the entire range of ports (1-65535)
as I have taken these over from someone else and am not sure what all
the wierd things they have runnin on these boxes on strange ports are.
Can anyone shed some light on how I can diminish the open sockets
issue and thereby speed up the scan process? In NessusWX I have
selected Nessus TCP Scan and nmap.nasl (with Syn scan) as my scan
options. Is this wise? Should I only be using one of the two? I ran
test nmaps against one of the two boxes and the nmap took over 30
minutes so i'm assuming it has something to do with that as well. Any
tips/pointer??

JZ
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus