Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
Thanks for the reply John. I suspected that continuing with short filenames was going to be the case, which is what we have been, and are currently doing. So no big difference there. We don’t use the msi file, we do the install ourselves from the zip file, so I think all we need to do is make sure that for the 64bit version that the registry entries go into the 64 bit section rather than the 32 bit. Cheers Greg From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of John M Knoeller Hi Greg. The Linux roots of condor are showing here. A lot of special case code is required to make spaces in path names work, On Windows this is mostly by using "" in appropriate places on the command
line and/or configuration. But If we were to use "" in all of the places that we needed to that would break HTCondor on Linux. Handling spaces in pathnames is just not something Linux developers even think about. It would actually be a violation of normal practice to do this on Linux for most of the paths that Condor
cares about. And the way a command line is modified to make those imbedded spaces work is never to put "" around the filename. So because we have common code between Windows and Linux the use of "short" pathnames on Windows will probably always be our solution
to this problem. We don't recommend you install Condor under "Program Files" to begin with, but if you do so, you must configure LOCAL_DIR and RELEASE_DIR to use the short path equivalent of those names. -tj From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Hitchen, Greg (IM&T, Kensington WA) <Greg.Hitchen@xxxxxxxx> Hi All Mentioned in a recent previous thread, but starting a new email subject specifically to do with directory paths containing spaces for the Windows version of HTCondor. The reason being that I would like to transition from our current production setup using the 32 bit version to the 64 bit version. I would also like to get rid of all the references in our current setup to: c:\progra~1\condor and change them to: c:\program files\condor Testing seems to mainly work, i.e. an install into “C:\Program Files\Condor” works with a condor_config entry of: RELEASE_DIR = C:\Program Files\Condor LOCAL_DIR = C:\Program Files\Condor LOCAL_CONFIG_FILE = $(LOCAL_DIR)/condor_config.local There is a problem with the condor_config.local folder though, as can be seen from these entries in the MasterLog and StartLog: 09/02/21 16:25:16 Using config source: c:\Program Files\condor\condor_config 09/02/21 16:25:16 Using local config sources:
09/02/21 16:25:16 C:\Program 09/02/21 16:25:16 Files\Condor/condor_config.local 09/02/21 16:25:16 config Macros = 192, Sorted = 192, StringBytes = 6019, TablesBytes = 6952 This was for the 64bit 8.8.12 version. Same result with 9.0.5 Confirmed by adding an entry to condor_config.local that is ignored by HTCondor. It is also not seen using condor_config_val -dump -verbose Other issues include this in StarterLog: 09/02/21 16:13:09 FILETRANSFER: Failed to execute C:\Program, ignoring 09/02/21 16:13:09 FILETRANSFER: failed to add plugin "C:\Program" because: FILETRANSFER:1:Failed to execute C:\Program, ignoring 09/02/21 16:13:09 my_popen: CreateProcess failed err=2 09/02/21 16:13:09 FILETRANSFER: Failed to execute Files\Condor/bin\curl_plugin.exe, ignoring 09/02/21 16:13:09 FILETRANSFER: failed to add plugin "Files\Condor/bin\curl_plugin.exe" because: FILETRANSFER:1:Failed to execute Files\Condor/bin\curl_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program
-classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 09/02/21 16:13:09 my_popen: CreateProcess failed err=2 In addition, I’m not certain that the benchmarking is working. From StartLog: 09/02/21 16:48:22 CronJobList: Adding job 'kflops' 09/02/21 16:48:22 CronJobList: Adding job 'mips' 09/02/21 16:48:22 CronJob: Initializing job 'kflops' (C:\Program Files\Condor/bin\condor_kflops.exe) 09/02/21 16:48:22 CronJob: Initializing job 'mips' (C:\Program Files\Condor/bin\condor_mips.exe) But I don’t seem to see those processes running. Shutting down HTCondor “much” later and it appears it thinks that the benchmarking is still going on: 09/02/21 17:01:54 Got SIGQUIT. Performing fast shutdown. 09/02/21 17:01:54 shutdown fast 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 Killing job kflops 09/02/21 17:01:54 Killing job mips 09/02/21 17:01:54 Deleting cron job manager 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 CronJobList: Deleting all jobs 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 CronJobList: Deleting all jobs 09/02/21 17:01:54 Deleting benchmark job mgr 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 Killing job kflops 09/02/21 17:01:54 Killing job mips 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 Killing job kflops 09/02/21 17:01:54 Killing job mips 09/02/21 17:01:54 CronJobList: Deleting all jobs 09/02/21 17:01:54 CronJobList: Deleting job 'kflops' 09/02/21 17:01:54 CronJob: Deleting job 'kflops' (C:\Program Files\Condor/bin\condor_kflops.exe), timer -1 09/02/21 17:01:54 CronJobList: Deleting job 'mips' 09/02/21 17:01:54 CronJob: Deleting job 'mips' (C:\Program Files\Condor/bin\condor_mips.exe), timer -1 09/02/21 17:01:54 Cron: Killing all jobs 09/02/21 17:01:54 CronJobList: Deleting all jobs Running them standalone in a cmd prompt works fine: C:\>"c:\Program Files\Condor\bin\condor_kflops.exe" KFlops = 1174379 -- C:\>"c:\Program Files\Condor\bin\condor_mips.exe" Mips = 5357 -- Thanks for any info/comments/help. Cheers Greg |