Re: [Condor-users] $ENV() in condor_config windows version 7.4.3 issues

[<Ian.Lecoultre@xxxxxxxx>]

Thanks everyone. The mklink will be a workaround. 

We just need to get the symlink in the script for 64 bit machines. That is our problem.

I knew something like this would work because making a copy of condor into the program files dir worked. (Only for testing) 

I just used: mklink /d condor "c:\program files (x86)\condor" 

Maybe the Condor group can get this on the list of known bugs. ;-) 

For those interested. In Windows 7 64 bit,
When we use %programfiles% (which resolves to c:\Program Files on the machine) in the copy statements in the kix32 script the windows 64bit machines put the files in the Program Files (x86) directory. The corresponding registry entries in Wow6432Node part of the registry have the appropriate path statements to the x86 directory, but when we use sc to put in the service that does not go into the Wow6432Node section but into the normal services section and gives the c:\Program Files path which of course does not work. Not sure how windows 7 distinguishes between the two? 

Regards,

Ian 


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Burnett, Ben
Sent: Friday, 1 October 2010 1:06 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] $ENV() in condor_config windows version 7.4.3 issues

In the mean time, to fix your problem, you can create a symbolic link c:\condor that points to the installed location.  Most recent versions of Windows ship with a tool for making symbolic links: mklink. You could even add this as a final step in the kixtart script (the name of that language brought back a few old memories-I remember writing a lot of scripts in that language), after the condor software is installed.

-B

On 2010-09-30, at 10:08 PM, <Ian.Lecoultre@xxxxxxxx> <Ian.Lecoultre@xxxxxxxx> wrote:

> Hi Ben,
> 
> Thanks for the suggestion. That only gives
> 
> ERROR: Can't read config source "C:\Program
> 
> We have tried quotes in many different locations. :-(  As you can see it stops at the space.
> 
> It appears that whatever code evaluates the RELEASE_DIR and LOCAL_DIR variables works but whatever evaluates the LOCAL_CONFIG_FILE cannot handle the space?
> 
> Regards,
> 
> Ian (working with Greg).
> 
> 
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Burnett, Ben
> Sent: Friday, 1 October 2010 11:47 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] $ENV() in condor_config windows version 7.4.3 issues
> 
> Try using:
> 
> LOCAL_CONFIG_FILE = "$ENV(ProgramFiles)\condor\condor_config.local"
> 
> -B
> 
> On 2010-09-29, at 11:33 PM, <Greg.Hitchen@xxxxxxxx> <Greg.Hitchen@xxxxxxxx> wrote:
> 
>> Hi All
>> 
>> We've been experimenting with the use of the special macro $ENV(environment_variable) in
>> our condor_config file. This issue has come about with 64 bit PCs starting to come online in
>> our pool of machines. We have hard-coded in our condor_config file the following:
>> 
>> RELEASE_DIR = C:\PROGRA~1\condor
>> LOCAL_DIR = C:\PROGRA~1\condor
>> LOCAL_CONFIG_FILE = $(LOCAL_DIR)\condor_config.local
>> However our kixstart install script installs into %PROGRAMFILES% and on 64 bit windows
>> this is "c:\program files (x86)" (which becomes c:\progra~2). So we've tried the following:
>> 
>> RELEASE_DIR = $ENV(ProgramFiles)\condor
>> LOCAL_DIR = $ENV(ProgramFiles)\condor
>> LOCAL_CONFIG_FILE = $ENV(ProgramFiles)\condor\condor_config.local
>> 
>> This works fine for the release_dir and the local_dir BUT NOT for local_config_file.
>> Using "condor_config_val -dump" gives:
>> 
>> ERROR: Can't read config source C:\Program
>> 
>> so it appears to be struggling with the whitespace in "C:\Program Files"
>> 
>> Note that trying other ways such as using:
>> 
>> LOCAL_CONFIG_FILE = $(LOCAL_DIR)\condor_config.local
>> or
>> LOCAL_CONFIG_FILE = C:\Program Files\condor\condor_config.local
>> have the same issue.
>> 
>> Has anyone else used this $ENV and /or come across this problem.
>> Can anyone confirm if this is a "bug" or do I need to do something different?
>> 
>> Thanks for any help.
>> 
>> Cheers
>> 
>> Greg
>> _______________________________________________
>> 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/
> 
> --
> Ben Burnett
> Department of Math & Computer Science
> Optimization Research Group
> University of Lethbridge
> http://optimization.cs.uleth.ca
> 
> 
> 
> _______________________________________________
> 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/
> _______________________________________________
> 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/

--
Ben Burnett
Department of Math & Computer Science
Optimization Research Group
University of Lethbridge
http://optimization.cs.uleth.ca



_______________________________________________
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/