First, crontab doesn't invoke a shell for you, so your environment variables, paths, etc. aren't going to be set up the way you want. That may be part of your problem.
However, what prompted me to post is the use of sudo in your crontab. Why not just use sudo to put the job in the proper user's (bibatch) crontab? Then things would be a bit less Rube Goldbergesqueified.
...roboticus
In reply to Re: Perl script in crontab
by roboticus
in thread Perl script in crontab
by AbraKdabra
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |