Ahem, I´d really like to help, but without
any
hint on the type of failure, it will be impossible.
Surely you´ll agree that the possibilities for failure
are countless, even on a properly configured system
(let alone a bad or
BOFH system;
<BOFH>
think of it: configure cron to run with
a chroot environment, the users will never figure out
what´s the problem! {veg}
</BOFH>
).
To aid your search for information:
- There should be a mail,
sent to root, after the failure of one or more cron
jobs. Look there for exit codes and/or messages.
- Rewrite your script to send a message to the
syslog (or a file in /tmp, use a unique name including
a timestamp) first thing (even before useing
libraries. If you get the message, your script did start
up and found a perl interpreter, so put in new debug
messages. Otherwise, your perl installation might not
be in the search path.
If you got more details, post a followup. We´ll be here :-).
Have fun ...
Andreas
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.