On Apr 29, 2008, at 9:14 AM, [EMAIL PROTECTED] wrote: > If I put the same script into a cron entry and force it to > run via ksh instead of sh - (although it does not seem to > matter) the script gets a segmentation fault when it hits > the first nessus command.
Is it possible the cron job is calling a different Nessus client (say because of differences in the PATH), say one that doesn't work any more? Or that you're loading a different client config file? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
