Description

Should the job daemon be running all the time, or is it OK to stop it?

Resolution

Though you need to restart the job daemon to make changes to the job_list take effect, the only reason to *stop* the job daemon is to avoid releasing jobs with a jobd started under the old time when there's a change to/from Daylight Savings Time. (See the articles " Clock change: Change to Daylight Savings Time (in the Spring) " and " Clock change problems with the switch off Daylight Savings Time (in the Fall) ".)   With this exception almost all sites leave the job daemon running all the time. 

Since seems that there might be an an effect on running jobs (not in the batch queue) of stopping the job daemon, we suggest that you stop/restart the job daemon only when jobs are not running. 

• Article last edited: 21-Feb-2018