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.
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.