Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Behaviour of Windows "copy" command?
- Date: Mon, 27 Jun 2005 19:13:37 +0100 (BST)
- From: Bruce Beckles <mbb10@xxxxxxxxx>
- Subject: Re: [Condor-users] Behaviour of Windows "copy" command?
On Mon, 27 Jun 2005, Nick Partner wrote:
The
mkdir poop
set TEMP=poop
idea is almost certainly the best thing to do since then it gets cleared up by condor! Remember that after 1000 jobs or more disks start filling up and even with small files it can be a problem after a while
That of course assumes that the working directory when those commands are
issued (and actually, for the entirety of the job's lifetime) is the
Condor job's execute directory. That's a dangerous assumption. If it
were me at the very least I'd be making sure that TEMP was set to a full
path not a relative one.
(And of course you have to remember to copy/move any files you want
returned when the job completes to the Condor job's execute directory,
otherwise Condor won't return them for you (but, in this scenario, they
still will be deleted whether or not they are returned!).)
-- Bruce
--
Bruce Beckles,
e-Science Specialist,
University of Cambridge Computing Service.