On Thu, May 1, 2008 10:47 am, Kat wrote: > Hi > > For those who are interested - the solution to the strange > seg fault problem: > > Seems my other "soon to be ex" admin had been playing > around with some profile type scripts and made some path > changes. He had also been working on his own 'nessus' > programs and when he made the path change a program he had > been writing for the client, was called instead of the > standard nessus command. The problem was simple -- > > In his program he had a call to getlogin() function, which > of course, under cron returns a null pointer. He was nto > checking this and was returned the function call directly > via strcpy - poof - seg fault! > > Thanks for the suggestions, but in the end - it was a bad > sys admin that was doing things he should not have been > doing. He will be more closely monitored from now on.. > *sigh* >
blaming others always makes me feel better too. micromanagement is the way out of that problem! </snark> _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
