As the previous poster said, it is important to know what is causing the jobs to restart. If the jobs are getting preempted on a dedicated pool, you can definitely change the configuration so that it never preempts running jobs and allows them to finish. If you are using cycle scavenging from desktops, you may be able to work out a policy that simply renices the job instead of evicting it so that the desktop user doesn’t notice any performance problems.
-Mick
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Peter Ellevseth
Sent: Wednesday, November 16, 2011 2:24 AM
To: Condor-Users Mail List
Subject: [Condor-users] Avoid restarting of jobs
Hi
We have some jobs that print out results continously while running in condor. If something happens to the job, then condor restarts the job. This is very unpractical as the previous results will then be overwritten. Is there a way to force condor not to restart the jobs? It would be preferable to us if the job exits instead of restarting.
Regards Peter
_______________________________________________
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/