I would have to agree with
kirillm for the most part. When a script runs on the command line but fails in crontab, it's usually an
environment variable issue. The cron environment is very limited and it does not inherit the settings from your login shell, unless you take a lot of care and trouble to make it happen.
The posters above have given suggestions to get your script to give up error messages and place them into files to be read. What I'll add is that you can get your environment variables, if you're in bash/ksh, with the command:
set
and that you probably should, while you're debugging your script, add something like:
print `set`;
into your script, just to see what the cron environment is (assuming you've redirected your script output to a file as others have suggested).
Finally, one style suggestion. It is much easier to do date manipulations with a module such as
Date::Calc or
Date::Manip than manually.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.