Re: (OT) Path Trouble

Replies are listed 'Best First'.
Re^2: (OT) Path Trouble by tc1364 (Beadle) on Mar 02, 2006 at 18:57 UTC
Yes and it is there. Please see below. # CSCANS Automation 45 12 * * 0-6 /ossd/tc1364/cscans/bin/start_cscans.pl	[reply]
Re^3: (OT) Path Trouble by philcrow (Priest) on Mar 02, 2006 at 19:05 UTC
I don't mean just in the cron entry. I also mean inside that script, whenever it refers to other scripts, the paths used are all absolute. Phil	[reply]
Re^4: (OT) Path Trouble by tc1364 (Beadle) on Mar 02, 2006 at 19:56 UTC
yes they are. Please see below. $bin = "/ossd/tc1364/cscans/bin"; $dms_start = "$bin/dms_start.exp"; $ess_start = "$bin/ess_start.exp"; $dms_pb = "/sys/extract/menu/west.pl";	[reply]
Re^4: (OT) Path Trouble by madizen (Sexton) on Mar 04, 2006 at 05:24 UTC
Part of my job is to babysit cron jobs and I totally agree. The secret to environmental harmony is to be independent of it to the extent possible. foo($path) needs to act on a /full/path . Since you're sure you're doing that I agree $ENV{LD_LIBRARY_PATH} is a place where you can still get hit by this.	[reply]