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

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

On Mon, 27 Jun 2005, Kewley, J (John) wrote:

If you have tight control over the Windows machines, you can create a
small NTFS volume with the appropriate permissions and mount
it to more or
less any directory path you like (this is supported from at
least Windows
2000 onwards).  That would obviously have to be set up in
advance and is a
truly horrible workaround, but it would do it...

-- Bruce

Getting at network drives can be tricky under Condor unless you are either running under your own user or your condor user has permissions to access the remote drives.

Indeed, but I wasn't thinking of a network drive: I was thinking of a local partition on each machine that you set aside for the application with the hard-coded paths (after, of course, you had shot the application's developer for incompetence). That's why I said you needed "tight control" over the Windows machines. You set up these local partitions and then mount them in advance. Then when the Condor runs the application, the application can write to the hard-coded place.

I'm not recommending this - it's horrible - just saying that it is a possible workaround.

	-- B

Bruce Beckles,
e-Science Specialist,
University of Cambridge Computing Service.