On Wed, Feb 05, 2003 at 11:43:42PM +0100, Paolo Poletti wrote: > Ii've modified the code of nmap_wrapper.c to do some debug and i've > found that the problem > come from the nmap pipe. > The problem arise from the fgets() call into the read_nmap_output() : > sometimes it fail, returning errno = EINTR (Interrupted system call) > during the first fgets() call of the scan. ... > However i don't understand > why nmap behave in a so strange way ....
Have you tried using strace to see what's going on? For example, given
that you're running Red Hat, the following should work:
strace -ff -o /tmp/strace.nessusd -p `pidof nessusd`
assuming you've only got one nessusd process running. This will output
trace info in files called /tmp/strace.nessusd.<pid>, one for the main
nessusd and one for each child process spawned by the daemon.
Btw, is there a chance nessus-update-plugins is being run while you're
doing these scans and experiencing these failures?
George
--
[EMAIL PROTECTED]
msg03481/pgp00000.pgp
Description: PGP signature
