Hi,
nessus just killed my machine by running a kill(-1, SIGTERM)!
Problem was that I could not fork and thus got a -1 as PID from
"create_thread()":
[Wed Jun 19 12:14:02 2002][15933] Error : could not fork ! Error : Not
enough space
[Wed Jun 19 12:14:02 2002][15933] user tbd : launching
logins.nasl<10870> against 192.168.110.178 [-1]
....
[Wed Jun 19 12:19:23 2002][15933] logins.nasl (pid -1) is slow to finish
- killing it
[Wed Jun 19 12:19:26 2002][14471] received the TERM signal
While investigating I also saw that the return value "-1" from
"next_free_process()" is not handled correctly: the caller doesn't check
and uses it as an array index, overwriting some other memory.
Not sure what to do with the fork problem, for now I will just exit
nessusd (so that at least my machine survives).
--nk
nessus just killed my machine by running a kill(-1, SIGTERM)!
Problem was that I could not fork and thus got a -1 as PID from
"create_thread()":
[Wed Jun 19 12:14:02 2002][15933] Error : could not fork ! Error : Not
enough space
[Wed Jun 19 12:14:02 2002][15933] user tbd : launching
logins.nasl<10870> against 192.168.110.178 [-1]
....
[Wed Jun 19 12:19:23 2002][15933] logins.nasl (pid -1) is slow to finish
- killing it
[Wed Jun 19 12:19:26 2002][14471] received the TERM signal
While investigating I also saw that the return value "-1" from
"next_free_process()" is not handled correctly: the caller doesn't check
and uses it as an array index, overwriting some other memory.
Not sure what to do with the fork problem, for now I will just exit
nessusd (so that at least my machine survives).
--nk