in reply to Re^3: possible perl5.8.7 bug?
in thread possible perl5.8.7 bug?

Unfortunately runme.sh has to have this form for cron:

exec perl5.8.7 cronmgr.pl < /dev/null >&0 2>&0

and, of course, I cannot even pass back a useful exit value from cronmgr.pl because it is always seen as null (as long as the 5.8.7 interpreter itself fires ok, which it does!). And leaving out the chaining effect of exec, other subsequent commands in runme.sh will execute ok too.

But food for thought on the config issues after a cron upgrade, if that doesn't help.

cheers

Pstack