Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
Hi Joaquin:
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:
condor_ssh_to_job cluster.proc
Where 'cluster' is the cluster id, and 'proc' is the process.
Best,
-B
> _______________________________________________
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
> debug)
>
> Regards
> --
> 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
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/