Subject: Re: [Condor-users] $ENV() in condor_config windows version 7.4.3 issues
I think this may be a bug with Condor
because I could not get paths to work when they have spaces for Java. I
also tried every combination as well as what is in the Condor manual and
nothing worked. Our set up for Condor is located on C:\Condor and therefore
we did not have a problem specifying the local config path. I am curious
if anyone else is having these problems with Windows, because I would like
to resolve the issue with specifying the Java path.
Mike
From:
<Ian.Lecoultre@xxxxxxxx>
To:
<condor-users@xxxxxxxxxxx>
Date:
09/30/2010 10:12 PM
Subject:
Re: [Condor-users] $ENV() in condor_config
windows version 7.4.3
issues
Sent by:
condor-users-bounces@xxxxxxxxxxx
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
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