[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Absolute and relative paths on Windows.
- Date: Mon, 14 Mar 2005 16:56:53 -0000
- From: "Sanjay Vivek" <smv99r@xxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Absolute and relative paths on Windows.
I've tried what you suggested but it's still not working. The job has been
running for about 50 mins and I still don't see any sort of output. As far
as I can tell, the job is running but it's not exactly doing anything. Is
there any way of finding out what's going wrong? Does this mean that the
exectuable isn't picking up ../../../ENKF/parameter/combine.ipf ??
----- Original Message -----
From: "Matt Hope" <matthew.hope@xxxxxxxxx>
To: "Condor-Users Mail List" <condor-users@xxxxxxxxxxx>
Sent: Monday, March 14, 2005 3:08 PM
Subject: Re: [Condor-users] Absolute and relative paths on Windows.
> On Mon, 14 Mar 2005 14:59:10 -0000, Sanjay Vivek <smv99r@xxxxxxxxxxxxxxx>
> > Hi everyone,
> > I'm a Condon newbie and I've a question about using absolute and
> > paths on Windows. Basically, I want to submit a job to Condor but the
> > executable and argument files are in different paths. The format of the
> > submit file is given below. I've tried various ways of writing the
> > path with respect to Windows but nothing seems to work. Basically, this
> > email is more about how to specify relative and absolute paths when it
> > to Windows. As shown below, Ifrf.exe is in C:\Program Files\isis\bin
> > combine.ipf is in C:\ENKF\parameter . Once I actually submit the submit
> > file, the job just runs forever and doesn't stop. This probably means
> > the executable isn't picking up the argument file, which in this case is
> > combine.ipf. Although putting the executable and argument file in the
> > path would have been an easier option, this is not feasible in my case
> > specific reasons. Besides, it shouldn't be too much of a problem
> > different paths for the executable and argument files (I hope not
> > Someone told me that the "../../../" might be messing things up. Any
> > help in this matter would be greatly appreciated. Thank you.
> > executable = Ifrf.exe
> > universe = vanilla
> > arguments = ../../../ENKF/parameter/combine.ipf
> > output = test.out
> > error = test.error
> > log = test.log
> > queue
> I think you may bhe misunderstanding the argumnets parameter.
> this specifies the texttual arguments passed to your process on startup.
> If you wish this file to be physically transfered as well you need to
> do something like
> executable = Ifrf.exe
> universe = vanilla
> transfer_input_files = ../../../ENKF/parameter/combine.ipf
> arguments = combine.ipf
> output = test.out
> error = test.error
> log = test.log
> note the additional transfer_input_files and the removal of the
> directory path from the arguments (I'm pretty sure on transfer that
> the path structure is flattened but I don't use this functionality
> with differing paths so couldn't say for sure...
> This should do whatever you need it to.
> I would suggest a read of the following would be beneficial:
> Condor-users mailing list