Re: [Condor-users] Installing Condor in C:\Program Files

[Bruce Beckles <mbb10@xxxxxxxxx>]

On Fri, 13 Oct 2006, James Osborne wrote:

> Does anybody have any experience of installing Condor 6.6.11 on windows into
> C:\Program Files\Condor directory, I know the installer defaults to C:\Condor
> but has anybody got it to work when installing it elsewhere in the filesystem,
> the reasoning behind why (tidiness) and the things I have tried to get Condor to
> work after installation into C:\Program Files\Condor

I haven't done this, but experience with similar badly behaved beasts 
suggests you'll be fine if you use the short form of the directory name 
for any directory with spaces.

Unfortunatley, you can't *predict* what the short form will be from the 
LFN (long file name), but for "Program Files" it will almost always be 
"PROGRA~1".  For any given directory, you can find out what it is by 
starting a command prompt and using the "dir" command with the "/x" 
switch, e.g., for "C:\Program Files", I would type the following at the 
command prompt:

dir "C:\Program File?" /x

(Note that the directory name is surrounded in quotes and I've replaced
 the last character with a question mark (?) - that is *deliberate*.  If
 you don't surround filenames or directory names that have spaces in them
 with quotes then the dir command won't understand them.  If you give it
 the full name of the directory then it will give you a listing of that
 directory.  If you only give it a partial name and a wildcard then it
 thinks you are searching the directory *above* for an entry which matches
 the partial name and hence will give you information about the desired
 directory (and any others that might match).)

which on my system produces the following output:

20/06/2004  13:14       <DIR>          PROGRA~1        Program Files

The short file name ("PROGRA~1") is in the fourth column across.
(Note that if that fourth column is blank, then that means the LFN is a
 valid short file name and so the system does not need to generate a short
 file name for it.)


There are clearly other ways of getting this information, and there must 
be a programmatic interface somewhere which allows you to get this 
information for any given file or directory, but I don't what it is. 
Google.

So if you set the registery entries for

CONDOR_CONFIG	to	C:\PROGRA~1\Condor\condor_config
		 &
RELEASE_DIR	to	C:\PROGRA~1\Condor

(Replace "PROGRA~1" with whatever the short file name for "C:\PRogram
 Files" is on your system.)

...then I suspect it will just work!


To the Condor Team: how about supporting filenames and path names with
                    spaces in them under Windows? :)

                    You could always put in a hack that read the config
                    file/registry entries and converted LFNs to their
                    short form if it would be too major a project
                    to make the code behave properly everywhere it reads
                    or writes files.

Anyway, hope the above helps someone - apologies if it is not as clearly 
expressed as it might be! :)

	-- Bruce

--
Bruce Beckles,
e-Science Specialist,
University of Cambridge Computing Service.