Page History

...

• The use of both SIGTERM and SIGKILL signals on Unix servers has the following advantages:

  • The use of SIGTERM before SIGKILL means that there is a greater chance of data being saved after the signal has been issued.

  • The SIGTERM signal can - in contrast with SIGKILL - be monitored, i.e. a pre-/ post-processing Script can be carried out. This means that the ending of a task by the JobScheduler can be reacted to and the user process itself can be ended.

  • The implementation of SIGTERM allows post-processing methods such as spooler_process_after() to complete within the timeout period.

• The time allowed between the SIGTERM and SIGKILL signals can be specified in the command using the timeout attribute (the default is 15 sec): <kill_task … timeout=".."/>

• This feature can also be applied for:
  • remote processes, i.e. processes started by SSH and those started by an Agent,
  • child processes started by a process running on an agent (JS-1468).

...

	Windows Standalone	Linux Standalone	Windows Classic Agent	Linux Classic Agent	Windows Universal Agent	Linux Universal Agent
Shell job
Terminate	not supported		not supported	JS-1420	not supported
Kill				JS-1421	JS-1468	JS-1468
Timeout	JS-1463	JS-1463				JS-1468
Shell job with monitor
Terminate	not supported		not supported		not supported	JS-1468
Kill					JS-1382	JS-1468
Timeout						JS-1382
API job
Terminate	not supported		not supported		not supported
Kill
Timeout

Task Termination in JOC

The following screenshot shows how a task can be terminated using the Task menu in JOC's Task pane. This pane is shown in the Jobs tab when the task is running and the task can be terminated either with timeout or immediately.

Image Added

Examples

Using a SIGTERM trap to show the difference between the kill and terminate commands

...