Re: [Condor-users] getenv = true not sending PATH environment variable in 7.2.0

["Thompson, Cooper" <cooper.thompson@xxxxxxxx>]

I'm seeing something funky with how PATH is getting passed through
Condor.  Using Process Explorer to look at the environment of a running
job, I see the following on my execute box:


For the condor_starter process, only one PATH environment variable:
	PATH=C:\test\path\that\does\not\exist;C:\Program
Files\Perl\bin\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;
C:\condor\bin

For the job_wrapper.bat process (set using USER_JOB_WRAPPER), TWO PATH
environment variables, PATH and Path (case being the differentiator)
	PATH=C:\test\path\that\does\not\exist;C:\Program
Files\Perl\bin\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;
C:\condor\bin
	Path=C:\Program
Files\Perl\bin\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;
C:\condor\bin

All child processes of the job_wrapper.bat also had two PATH entries.
It appears that when you echo %PATH%, it uses the PATH variable (rather
than Path), so you end up seeing the PATH from the execution machine.
PATH is used by Windows, so the Path set by Condor seems to be ignored.


Note: I added C:\test\path\that\does\not\exist to the path on my execute
machine only.


The submit file I used was:

executable = test.bat
run_as_owner = true
getenv = true
output = $(CLUSTER).output.log
error = $(CLUSTER).error.log
log = $(CLUSTER).log
queue


test.bat:
rem --------START------------
hostname
set

rem simple VBScript that just does WScript.Sleep 50000
rem so I have time to inspect the environment
C:\condor\bin\sleep.vbs
rem --------END--------------

Coop


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Matthew Farrellee
Sent: Thursday, January 15, 2009 11:09 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] getenv = true not sending PATH environment
variable in 7.2.0

Torrin Jones wrote:
>>  The code for grabbing the env hasn't changed since March 2007. You
>> didn't mention what version you are coming from.
>>
> 
> Thanks for getting back to me.  I don't think any of the characters
that you
> mentioned are in my PATH statement, but I'll check anyway.
> 
> These are the condor versions that I've used where the PATH
environment
> variable goes through . . .
> 
> 6.8.5
> 7.0.1
> 7.0.5
> 
> So basically, it "fails" on the newest stable version (7.2.0).  I
don't use
> development versions.

A quick diff suggests this code is the same in 7.0 and 7.2 (and 6.8.5 
for that matter) - so either the PATH is at fault or something else is 
going on.

Best,


matt
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: 
https://lists.cs.wisc.edu/archive/condor-users/