Michael Scheidell <[EMAIL PROTECTED]> writes: > so, its how FBSD handles signals....?
No, it must be a race condition or something like this. If I run nmap with the "standard port range", no probem. With 1-65535, I get a deadlock. The son process is locked into a select, waiting for the father to read on the socket. But it seems that the father does not look at this socket in check_threads_input I suspect a problem in the management of child processes... - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
