Re: (OT) Path Trouble

You may well find that PATH is not being set by cron as it is not sourcing in .bashrc or .profile - this is expected and normal behaviour.

You have access to PATH as $ENV{PATH}, which you can set inside your script before you fork. %ENV is available for dumping out for debugging purposes.

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

Comment on Re: (OT) Path Trouble

Replies are listed 'Best First'.
Re^2: (OT) Path Trouble by tc1364 (Beadle) on Mar 02, 2006 at 18:46 UTC
This was already tried and didn't work. The cron job returns the below. Also, the local to this object code is in my PATH. Your "cron" job on osdsun60 /ossd/tc1364/cscans/bin/start_cscans.pl produced the following output: ld.so.1: dms_start.exp: fatal: libtcl8.3.so: open failed: No such file or direct ory Killed commands will be executed using /usr/bin/sh job 1141324921.a at Thu Mar 2 12:42:01 2006	[reply]
Re^3: (OT) Path Trouble by rinceWind (Monsignor) on Mar 03, 2006 at 10:42 UTC
Looks from the diagnostic that the problem might be with $ENV{LD_LIBRARY_PATH} rather than $ENV{PATH}. Which flavour of Unix are you running? By the way, for readability, could you please put <code> tags around your output. -- Oh Lord, won’t you burn me a Knoppix CD ? My friends all rate Windows, I must disagree. Your powers of persuasion will set them all free, So oh Lord, won’t you burn me a Knoppix CD ? (Missquoting Janis Joplin)	[reply]