-
November 8th, 2005, 03:53 PM
#1
nessusd killing and and still getting the logs
Hello all-
I was looking through the man pages for nessus and could not find anything on this, but I was wondering if there is a "safe" way to terminate a nessus scan forked from a cron job?
Also - if killed, does NESSUS save off it's log files so that you can review them? We found some type of log files in /tmp, but we were wondering if there's another location to look as well?
Finally, if NESSUS crashes an application, or a server, is there a way, via the logs to see what plugin caused the incident?
Searching the NESSUS mail log yielded the following on the shutdown of the daemon - basically a init.d script setup:
http://mail.nessus.org/pipermail/nes.../msg00095.html
However, I wanted to see if there is an updated solution anyone here may have.
We are currently using NESSUS 2.2.4
Thanks in advance and let me know if I can provide anymore information.
\"We\'re the middle children of history.... no purpose or place. We have no Great War, no Great Depression. Our great war is a spiritual war. Our great depression is our lives. We\'ve all been raised by television to believe that one day we\'ll all be millionaires and movie gods and rock stars -- but we won\'t. And we\'re learning slowly that fact. And we\'re very, very pissed off.\" - Tyler (Brad Pitt) Fight Club.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|