You may need to provide a bit more information to solve this one. Do you have any output (logs) showing that the program/script attempted to run the nessus scan?
If you're not doing this already, one approach may be to use a cron job to fire off the scans. ... Inprotect has a good series of scripts to use for a baseline approach. ( http://sourceforge.net/projects/inprotect/ ) ---------------------------------------------------- Mike Sleeper CISSP, CCSE, CCFS Computer & Information Security 803.725.3100 803.725.PAGE (#13146) ---------------------------------------------------- ************* DISCLAIMER *********************************** The above comments are my own and do not necessarily represent those of my employer or contractor. Any information or advice provided by me shall be given under the "caveat emptor" principal. ***************************************************************** "Harvey, Jack" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/30/2007 10:52 AM To <[email protected]> cc Subject need direction I start nessusd from /etc/rc.local. Starts fine. I have a series of shell/c++ programs that do things like prepare the list of servers that will be scanned, check the time for the start of the scan, email the scan results, etc. If I am logged in, these work fine. I would like to start the main calling shell program from rc.local as well. If I do this, the nessus scan (from command line of course) never runs. It is skipped. All the rest of the programs complete…useless without the scan. Please point me in the right direction for running nessus NOT logged in… Jack _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
