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

Re: [HTCondor-users] process and timing for creating output file

On 3/24/2014 2:47 PM, Nathan W. Panike wrote:
submit tells the schedd, and the schedd attempts to create the file
(during the submit operation).

My recollection is different.... [ Nathan, see the call to safe_open_wrapper_follow() in submit.cpp:check_open() ... ]

I am quite certain that by default condor_submit will
  a) create (and/or truncate) the stdout file, then
b) ask the schedd if it can successfully access/open the file that condor_submit just created

This song and dance happens so HTCondor can report a wide array of file or directory permission problems to the user at submit time, instead of having to put the job on hold later once it is scheduled for execution.

Of course, there is a fair amount of overhead in all this error checking, esp if your submit machine is very busy. You can disable it a variety of way and thereby speed up the time it takes to submit jobs; Nathan listed two of them, I repeat those plus one more below.

So, Scott, the quick answer to your question below is the stdout/err file is indeed created by condor_submit UNLESS you disable file checking by condor_submit by doing either
  1. -disable command line option to condor_submit, OR
  2.  enter into condor_config SUBMIT_SKIP_FILECHECKS=true, OR
  3.  enter into your job submit file skip_filechecks = true