This sounds suspiciously like he ran out of memory and the kernel killed the process, no?
Is there anything reported via dmesg when this happens? Renaud, my next guess is there is a memory leak or lack of memory management being applied. David Renaud Deraison wrote: >On Sun, Aug 25, 2002 at 08:20:24PM +0200, Berlin, Christoph wrote: > > >> I tried to scan my network with the latest version of Nessus. After >> starting the scan, the Nessus client works. But 2 or 3 hours later, the >> process is killed. Nothing happens, there is no output (html) and my scan >> results are blown away :-( A Scan with one or two scan clients works and >> the result are perfect. >> >> -- I may have the information you need and I may choose only HTML. It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion. If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites. I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access. This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away. Don't be a cluebert, buy one from K-mart today. - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
