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

Re: [Condor-users] How To TroubleShoot Flocking

> ...
> >According to 6.7 manual :
> >  should_transfer_files = <YES | NO | IF_NEEDED >
> >
> >Is True a valid alternative?
> >  
> >
> Ah, good question.  I had to dig into the source code to find 
> out.  The 
> answer is that should_transfer_files=True is equivalent to 
> should_transfer_files=Yes.  I didn't realize my 
> recommendation relied on 
> an undocumented feature!

I suspected it was valid, but had never seen it before. All examples seem to

2.5.4 and section on condor_submit are where the documented features of this are
(at least in 6.7)

The choice of YES/NO over TRUE/FALSE is a good one. When people see
T/F they immediately thing of a 2-valued logic, so having someing other than
T/F is good when other values are allowed.

I believe these values are case insensitive (but I don't have the luxury of
the code to check!)

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 combination is
 prohibited by condor_submit."

It is obviously something obvious, but I haven't twigged it yet.

If you are on a system where some machines are in same FileSystemDomain and some aren't,
you may still want (possibly in)complete files to be returned regardless of how job