[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Absolute and relative paths on Windows.

Sanjay Vivek <smv99r@xxxxxxxxxxxxxxx> wrote:
> executable         = Ifrf.exe
> universe             = vanilla 
> arguments          = ../../../ENKF/parameter/combine.ipf            
> output                = test.out
> error                   = test.error             
> log                     = test.log  
> queue  

Matt Hope had some good comments, I just wanted to clarify a few

First, and perhaps most importantly, Condor is going to copy your
executable into a temporary directory (EXECUTE/dir_$PID: omething like
C:\Condor\execute\dir_12359\)  Thus, relative paths (like
../../../ENKF) are unlikely to work.  If you want to provide
paths to your program in this way, you need to provide full

Matt is correct, for most production deployments of Condor on
Windows, you'll want to use file transfer.  Any files you
specify in transfer_input_files will be copied into the temporary
directory mentioned above.  The path will be flattened.  So
Matt's suggestion of something like this is correct:

> arguments=combine.ipf
> transfer_input_files=C:\foo\bar\ENKF\parameter\combine.ipf

Again, note the need to use full paths.  A relative path might
work, but it would be relative to the current working directory
of the condor_schedd; probably not what you want. (Indeed, it
will likely be whatever LOG is set to in your config files.)

Details on the file transfer mechanism are here:

Standard output (output=test.out) is typically not spooled back
to the submit machine until the job finishes.

Alan De Smet                              Condor Project Research
adesmet@xxxxxxxxxxx                 http://www.condorproject.org/