in reply to use lib 'foo/bar' in cron-called script...

Have your script try to open the file. Then it will know what error the perl library loader is seeing: 
open MYLIBRARY,"/opt/ipcwww/data/lab/tcreports/ims/bin" or die "Ack, f
+ile trouble: $!";

[download]
Hopefully that will let you know whether it's a permission problem, or a library path problem ($! should tell you what's going down). Good luck.

    --jb

Replies are listed 'Best First'.
Re: Re: use lib 'foo/bar' in cron-called script...
by rje (Deacon) on Jun 06, 2002 at 21:47 UTC
    Thank you. This was a good suggestion.

    What I've actually done is something that Abigail-II
    suggested: I'm running the scripts from my own crontab,
    thus bypassing my co-worker's crontab woes. This actually
    makes more sense anyhow, since I own the perl files.

    Anyhow, from my own crontab things run just fine.
    Permissions and paths all appear to be fine... at least
    I'm getting the expected output now.

    -Rob
    (maybe I'm not even at the user-level of proficiency, eh?)
    (it's been one of those weeks)
[reply]

In Section Seekers of Perl Wisdom