[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] How To TroubleShoot Flocking
- Date: Wed, 12 Jul 2006 17:33:10 -0500
- From: "John Alberts" <Alberts@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] How To TroubleShoot Flocking
Finally got it to work. What I did was create a small script called
gethost.sh that simply calls hostname, instead of directly running
For some reason, trying to just run hostname was causing the
condor_exec.exe failed error message. I'll have to do some more
troubleshooting to determine if it was because no files were actually
transferred, or some problem/incompatibility with running hostname.
Thanks for all of the help.
Technical Assistant for EMS
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Erik Paulson
Sent: Tuesday, July 11, 2006 10:52 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] How To TroubleShoot Flocking
On Fri, Jul 07, 2006 at 03:46:00PM +0100, Kewley, J (John) wrote:
> I have still never quite worked out why
> "NOTE: The combination of:
> should_transfer_files = IF_NEEDED
> when_to_transfer_output = ON_EXIT_OR_EVICT
> would produce undefined file access semantics. Therefore, this
> prohibited by condor_submit."
> It is obviously something obvious, but I haven't twigged it yet.
To support transfering modified files, files in-flight live in the
directory, which is usually not shared. This can cause problems when
job runs on machines that need file transfer, get evicted, and starts
running again on a machine that does not need file transfer.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
You can also unsubscribe by visiting
The archives can be found at either