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

["Nathan W. Panike" <nathan.panike@xxxxxxxxx>]

errr, attempt_access()

On Tue, Mar 25, 2014 at 7:04 PM, Nathan W. Panike
<nathan.panike@xxxxxxxxx> wrote:
> Sorry, I was looking at TestFilePermissions --> allow_access()
>
> On Tue, Mar 25, 2014 at 3:39 PM, Scott Koranda <skoranda@xxxxxxxxx> wrote:
>> 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>
>>>> wrote:
>>>>>
>>>>> 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
>>>>>
>>>>
>>>> Thanks.
>>>>
>>>> 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,
>>> Todd
>>>
>>
>> It does, thanks. No need for a definitive follow up at this time.
>>
>> Cheers,
>>
>> Scott
>> _______________________________________________
>> HTCondor-users mailing list
>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/htcondor-users/
>
>
>
> --
> Nathan Panike



-- 
Nathan Panike