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

["John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>]

You are correct.  LOCAL_CONFIG_FILE is not handed like LOCAL_DIR and RELEASE_DIR.  In fact LOCAL_CONFIG_FILE is really sort of misnamed.  It should really be called LOCAL_CONFIG_FILES (plural).  It is defined as a comma or space separated list of local config files. 

The bad news is that the parser for this list pays no attention to single or double quotes (oops!).   It just blindly tokenizes the list on every space and/or comma.   It then treats each token as a filename.

So this is really a bug in Condor,  LOCAL_CONFIG_FILE will only accept file paths that have no spaces or commas in them.  The only workarounds involve handing LOCAL_CONFIG_FILE a path that contains no spaces.

Either use short pathnames like PROGRA~1\Condor\condor_config.local or use mklink (Vista and 7) or linkd (WinXP) to create symlinks or hardlinks to the condor folder or local config file.

I have added a ticket for this bug:
https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=1687

-tj

On 9/30/2010 11:40 PM, Ian.Lecoultre@xxxxxxxx wrote:

Hi Shahaan,

 

Yes that is an interesting one.

Using your

LOCAL_CONFIG_FILE = $(RELEASE_DIR)\condor_config.local

While

RELEASE_DIR = C:\PROGRA~1\condor

condor_config_val –dump returns

LOCAL_CONFIG_FILE = $(RELEASE_DIR)\condor_config.local

OK

But when we put in

RELEASE_DIR = $ENV(ProgramFiles)\condor

We get the same old

ERROR: Can't read config source C:\Program

 

Arrrrrr. I keep getting the idea LOCAL_CONFIG_FILE is not handling the string the same as RELEASE_DIR and LOCAL_DIR.

 

Regards,

 

Ian

 

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

 

Hi Ian,

  Try

LOCAL_CONFIG_FILE = $(RELEASE_DIR)\condor_config.local

 

regards,

 

Shahaan

 

On Fri, Oct 1, 2010 at 2:08 PM, <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/

 

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