[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] process and timing for creating output file
- Date: Tue, 25 Mar 2014 14:39:32 -0500
- From: Scott Koranda <skoranda@xxxxxxxxx>
- Subject: Re: [HTCondor-users] process and timing for creating output file
On Tue, Mar 25, 2014 at 2:35 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:
> On 3/25/2014 1:43 PM, Scott Koranda wrote:
>> On Tue, Mar 25, 2014 at 1:29 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx>
>>> So, Scott, the quick answer to your question below is the stdout/err file
>>> 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
>> Am I correct then that if I have used one of those options above the
>> file is created by the condor_shadow when the job enters the run
>> state? My testing shows that the file is not created when the job
>> immediately is put on hold nor when in the idle state, but it would be
>> helpful to have my theory confirmed.
> Hi Scott,
> Warning, this is from memory (don't have time right now to check
> definitively), but I believe if you use the disable option(s) above and you
> are running on a shared file system (e.g. no file transfer requested in your
> submit file), the stdout will be created by the condor_starter right before
> the job is launched.
> If you requested file transfer, or if you requested streaming of stdout to
> the submit machine, I think the file will created on the execute node by the
> condor_starter and then transferred over to a file on the execute machine
> that is created by the condor_shadow.
> Hope this helps,
It does, thanks. No need for a definitive follow up at this time.