Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Executable path and environment
- Date: Tue, 13 May 2008 12:15:02 -0700
- From: David Brodbeck <brodbd@xxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Executable path and environment
On May 12, 2008, at 1:34 PM, Ian Chesal wrote:
Actually, that doesn't work in my experience.
Even if you use "getenv = true" Condor doesn't seem
to use the submitting user's $PATH when searching for
executables.
Interesting. I just tried it here with 7.0.1 and yea, PATH is *not*
exported from my environment. I see the PATH that's defined in the
starter job environment config setting.
Condor team: is this a bug???
I'm using 6.8.8 on Linux, and that's not how it happens for me. The
environment gets exported OK, it's just that Condor doesn't use it
while searching for executables.
For example, this works, and shows the user's environment:
universe = vanilla
executable = /bin/bash
arguments = -c set
transfer_executable = false
getenv = true
output = set.out
log = /tmp/brodbd/set.log
Queue
But this gets held:
universe = vanilla
executable = bash
arguments = -c set
transfer_executable = false
getenv = true
output = set.out
log = /tmp/brodbd/set.log
Queue
The log file shows it's trying to find the executable in the current
directory, not using the search path:
000 (8875.000.000) 05/13 12:09:48 Job submitted from host:
<192.168.100.50:50116>
...
001 (8875.000.000) 05/13 12:09:55 Job executing on host:
<192.168.100.69:46672>
...
007 (8875.000.000) 05/13 12:09:55 Shadow exception!
Error from starter on vm1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: Failed to
execute '/home/brodbd/test/bash' with arguments -c set: No such file
or directory
0 - Run Bytes Sent By Job
0 - Run Bytes Received By Job
...
012 (8875.000.000) 05/13 12:09:55 Job was held.
Error from starter on vm1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx: Failed to
execute '/home/brodbd/test/bash' with arguments -c set: No such file
or directory
Code 6 Subcode 2
...
If there's a setting to change this behavior I'd like to know about
it. It's a common source of confusion for my users.
--
David Brodbeck
System Administrator, Linguistics
University of Washington