Jean
User
Aug 11, 2004, 11:37 AM
Post #1 of 3
(2246 views)
|
 Running script via cron fails on use statement
|
Can't Post
|
|
Hi All,
Haven't been here a while...
And here is the story for the interested:
Running some script via cron on Solaris gives me a totally different @INC compared to running it manually (root in both cases). The problem that is caused by different @INCs is that I can't use any use statement, even something like use strict.
I know that the Solaris 5.8 machines I tried to run the script on have some (identical) awkward Perl configuration, though running the script manually works fine  ... Meddling with the @INC (both use lib and BEGIN {unshift(@INC,'/any/path');}) causes the script to fail - again, only when it's being run via cron.
On one hand I could probably rewrite my custom modules to make .pl files out of them and simply remove use strict/warnings, but it just beats the purpose of modules and simply goes against my nature. On the other hand we're talking work here and I can't really spend years on making a script of several hundreds lines work (for now I've spent about 15 hours in the office today).
Spending major part of a day on debugging the script that took less than 2 hours to write is very discouraging (specially taking into account the fact that it really shines when run manually or inside while 1), but it's now a matter of principle - me against the cron  . Please help me not to loose to the soulless software 
Suggestions are very welcome.
Please feel free to contact me on jean@kashya[ANTI_S.P.A.M].com (w/o the [ANTI_S.P.A.M] part)
Thanks for even reading this,
Jean
Jean Spector
SQA Engineer @ Exanet
jean.spector@softhome.net
There are only 10 types of people in the world -
Those who understand binary, and those who don't.
|
MAIN
SEARCH
WHO'S 
LOG 
Re: [davorg] Running script via cron fails on use statement
[
.