Correct Stopping

The Job Scheduler stops when all jobs have come to an end.

See and .

Correct Stopping with a Time Limit

A time limit may be specified within which the Job Scheduler must stop. Should tasks still be running at the end of this time limit, because for example they remain too long in the then the Job Scheduler terminates all processes still running.

However the Job Scheduler first sends out an e-mail listing the tasks being terminated.

The Job Scheduler then waits a maximum 30 seconds for the tasks to terminate (this usually takes place immediately) before stopping itself.

See and .

Termination

The Job Scheduler breaks off all processes (including the foreign processes registered with add_pid()) immediately. (Unix: kill -s KILL, Windows: TerminateProcess()). The Job Scheduler then shuts itself down.

Advantage: The termination is immediate.

Disadvantage: the software, in particular the jobs, do not have the possibility to react. This means, for example, that temporary files cannot be deleted.