Good morning/afternoon/evening... I know this is not a nessus problem, but it is a long shot that someone may have an idea. Nessus of course runs flawlessly on a linux box I have. I run in command line mode for several scans, which, when I enter by hand work perfectly. I have even scripted some. Nothing strange or unusual, just that I am lazy since we do the same scans monthly..
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. has anyone run into things with cron causing something like this? A perfectly working script/program that causes a seg fault when run within cron? thanks _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
