[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Avoid to delete temporary files
- Date: Wed, 4 May 2011 23:12:25 +0200
- From: Joaquin Monedero <jadeade@xxxxxxxxx>
- Subject: Re: [Condor-users] Avoid to delete temporary files
Thank you Ben, that's what I wanted to know exactly, and that's what happen to me, the executes too fast to let me check it properly.
What if I cannot recompile? how could I add that sleep, maybe launching it from a script?
PD: condor_ssh_to_job command written down, looks really useful.
Ignorance is bliss
On Wed, May 4, 2011 at 22:40, Burnett, Ben <ben.burnett@xxxxxxxx>
By temporary files, I assume you mean the sand-box on the execute machine, correct? Rather than trying to disable the clean up, you can actually log in to the execute machine while it is running the job. If the job exits to quickly, you could add a long sleep to it at some point in the execution, to give you time to log in remotely.
Condor provides a really nice command line tool to jump on to the machine where your job is running. First, use condor_q to get the job cluster and process (or use the one printed on submit). Then, from the command line, run the following:
Where 'cluster' is the cluster id, and 'proc' is the process.
On 2011-05-04, at 1:38 PM, Joaquin Monedero wrote:
> Hi all
> Is there any way to avoid condor to delete temporary files? (in order to
> Ignorance is bliss
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at:
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: