Re: [Condor-users] Behaviour of Windows "copy" command?

["Nick Partner" <nick@xxxxxxxxxxxxxxxxxxxx>]

Hi,

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

Nick

PS. Note: win2k3+ env vars are case sensitive

-----Original Message-----
From: Matt Hope <matthew.hope@xxxxxxxxx>
Date: Mon, 27 Jun 2005 17:38:40 
To:Condor-Users Mail List <condor-users@xxxxxxxxxxx>
Subject: Re: [Condor-users] Behaviour of Windows "copy" command?

On 6/27/05, Rob Fletcher <rpf1@xxxxxxxxxx> wrote:
> On Mon, 27 Jun 2005, Bruce Beckles wrote:
> 
> Creating a c:\temp with full access for all users fixes the problem.
> 
> Of course, a per user directory in temp would also be useful for easy
> peasy cleaning up afterwards.

the windows behaviour on temp directories becomes more complex as you
go up the versions.
There are windows specific temp directories, sadly these are under you
'documents and settings' folder by default. I don't even know if these
can be overridden easily...
For example
C:\Documents and Settings\matth\Local Settings\Temp
Many applications (and .net functions) will use this for temporary
storage. Note that no such directory will exist for condor-reuse-vmx
created accounts.

If your application is at least using the TEMP or TMP environment
variable it is perfectly ok to change that at runtime via the script
to something under the SCRATCH directory...

> Some Mondays are just for hating Windows!

I reserve Fridays for that pleasure.

Matt

_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/condor-users