Re: [Condor-users] disabling file transfer in vanilla universe

[Claude Saunders <saunders@xxxxxxxxxxx>]

Todd Tannenbaum wrote:
> Claude Saunders wrote:
> >   Ian Chesal wrote:
> > > On Thu, Apr 22, 2010 at 5:02 PM, Claude Saunders 
> > > <saunders@xxxxxxxxxxx <mailto:saunders@xxxxxxxxxxx>> wrote:
> > >
> > >     It just so happens that I set it up so the executable in step (2)
> > >     above uses stdin and stdout to read and write the files. Given
> > >     that I'm taking care of the file transfers using gridftp
> > >     explicitly, I would like to disable the default condor file 
> > > transfer.
> > >
> > >     Here's my problem: I'm using vanilla universe, and setting
> > >     should_transfer_files=no and submitting the job to run on a
> > >     machine with a different file system. The job won't get run since
> > >     my.filesystemdomain != target.filesystemdomain, which appears to
> > >     be a default requirements test.
>
> condor_submit will add in the default requirement for filesystemdomain 
> only if you don't explicitly set it in the job's requirements.
>
> The idea is to make a requirements statement that references 
> FileSystemDomain and yet always evals to true. Something like the 
> following should work for you:
>
> should_transfer_files = never
> requirements = FileSystemDomain != "green_eggs_and_ham"
>
> regards and welcome to condor-users!
> Todd
Thanks, but I still cannot get the desired behavior (namely: disabling 
file transfer AND not making shared filesystem assumptions).

With the above suggestion you made, the job will now run, but it still 
assumes a shared filesystem. If my submit file says 
output=/some/directory/local/to/job/host/test.txt, the condor_submit 
fails immediately since it cannot find that directory on the submit 
host. If I simply put output=test.txt, then the job gets stuck in a HOLD 
since the job host cannot find the submit host filesystem after the 
scheduling. Even if my job doesn't use stdin/stdout/stderr, I still have 
the above problem with the log file.

What is desirable is to turn off file transfer, and also not make shared 
filesystem assumptions. It seems this is not possible at the moment.

   regards