One solution to this problem is to have the job sleep for at least POLLING_INTERVAL seconds before doing anything that should not be interrupted. Rather than requiring the job to be modified, the administrator can use USER_JOB_WRAPPER to do the sleeping before the job starts. -The file =whole_machine_job_wrapper= could then be created with the following contents. Adjust the setting of condor_history and sleep_time at the top of the script to be appropriate for your situation. Be sure to add execute and read permission to this file for all users. If you already have a USER_JOB_WRAPPER, you will need to merge together this new script with the existing one. +To accomplish that, the file =whole_machine_job_wrapper= should be created with the following contents. *Adjust the setting of condor_history and sleep_time at the top of the script to be appropriate for your situation. Be sure to add execute and read permission to this file for all users.* If you already have a USER_JOB_WRAPPER, you will need to merge together this new script with the existing one. {code} #!/bin/sh