Re: [Condor-users] zero-byte output files

[Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx>]

On 05/30/2012 04:03 PM, Matthew Farrellee wrote:
> On 05/30/2012 03:47 PM, Dimitri Maziuk wrote:
>> On 05/30/2012 02:18 PM, Dimitri Maziuk wrote:
>>> Hi everyone,
>>>
>>> quick question: does condor check for errors when writing the output
>>> files? (Or is that even usable on nfs?)
>>
>> I guess the first question is if condor's running a program that writes
>> its output file to /nfs/share/someplace, does condor interfere with that
>> output in any way, or should I be looking at that program instead?
> 
> Condor traps stdout and stderr (output & error, respectively, in your
> submit file). Condor won't interfere with files your job writes as output.
> 
> If you have output=/nfs/share/someplace/somefile in a submit file,
> Condor will think it has the right to write somefile. If your job
> happens to want to write the same file, you'll have a problem.

No, I have output = myjobname.stdout, not the same file as the zero-byte
one in question. So I should be looking at the program (BLAST) then.

Thanks
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Attachment: signature.asc
Description: OpenPGP digital signature