Hi, Thanks to this thread I found out why my script was failing with a similar error. All was fine with the root and user account, but failed when I sudo -u myser in root crontab. The @INC included (last, well hidden) the '.' which was actually... /root of course. So just a cd in the launching shell script and voila, but it took me too much effort and wasted time over this (stupid) new perl behaviour. I do not give a damn if @INC (or PATH, or LD_LIBRARY_PATH or WHATEVER PATH) includes a sometimes non-readable directory. My special thanks for the wasted time (and VERY unhappy clients of mine) to all the morons who coded this new perl behavior.
Why did you make an upgrade without testing first?
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||