Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] transfer output files back to the submit machine every hour
- Date: Thu, 20 Dec 2007 08:19:16 -0600
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [Condor-users] transfer output files back to the submit machine every hour
Martin Zonda wrote:
Hi
I want to ask if
it is possible to adjust Condor's File Transfer Mechanism for a long job
in such a way that Condor would transfer output files back to the submit
machine every hour (for example)?
If it is possible, how can I manage this?
Perhaps file streaming can help you? If the output you are interested
in viewing at your submit machine can find its way into the jobs stdout
or stderr, you could specify stream_output=True or stream_error=True in
your submit file. From the condor_submit man page:
stream_error = <True | False>
If True, then stderr is streamed back to the machine from which the
job was submitted. If False, stderr is stored locally and transferred
back when the job completes. This command is ignored if the job ClassAd
attribute TransferErr is False. The default value is True in the grid
universe and False otherwise.
stream_input = <True | False>
If True, then stdin is streamed from the machine on which the job
was submitted. The default value is False. The command is only relevant
for jobs submitted to the vanilla or java universes, and it is ignored
by the grid universe.
stream_output = <True | False>
If True, then stdout is streamed back to the machine from which the
job was submitted. If False, stdout is stored locally and transferred
back when the job completes. This command is ignored if the job ClassAd
attribute TransferOut is False. The default value is True in the grid
universe and False otherwise.
hope this help,
Todd