I attempted to create a script the will archive the nessusd.dump file and the nessusd.messages, because they fill up quickly. I’m running Nessus 2.0.12 . It works!!!  I gave myself a gold star, being that it’s one of my first real scripts. The only problem is the new nessusd.messages file is not populating with any data from new scans. What do I need to do to archive these files and keep the system running?

 

Here is the script I wrote that I added to a weekly cron:

 

#!/bin/bash
declare TARDATE=`date +%R-%F`
gzip -c9 /usr/local/var/nessus/logs/nessusd.dump >> nessusd.dump_$TARDATE.gz
gzip -c9 /usr/local/var/nessus/logs/nessusd.messages >> nessus.messages_$TARDATE.gz
mv /usr/local/var/nessus/logs/*.gz /usr/local/var/nessus/log_saves/
 
rm -rf /usr/local/var/nessus/logs/nessusd.dump nessusd.messages
touch /usr/local/var/nessus/logs/nessusd.dump nessusd.messages
chmod 644 /usr/local/var/nessus/logs/nessusd.dump nessusd.messages

 

 

 

Robert McGlon

Office of the Chief Information Security Officer (OCISO)

Centers for Disease Control and Prevention

(770) 488-8658

cdq1@cdc.gov

 

_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to