The last refuge in cases like this for me are to put debugging lines that write to the log file after *every* line in the offending script, or at least where I think in the area I think the bug is living. Even if no variables are supposed to change, at least put a "I am here" line in.
Also, lines like:
are your friends in cases like this.
But in case this is jumping just a bit ahead, are you able to run the suspected script outside of cron/whatever auto mechanism there is, correctly and consistently?
At 10:50 AM 2/5/2003 -0800, Michael Mehrle wrote:
>Well, putting '0,30 * * * * /etc/init.d/slash keepalive' into my crontab didn't work. I'm getting really frustrated - can anyone offer any advice or suggestions?
>Any help would be appreciated - I have been working on this day and night and cannot go live without fixing this... if anyone needs more details, please look at my previous postings since Sunday.
>Cheers and thanks in advance....