Page History

Table of Contents
outlinh1. true outlinh1. true 1 printablefalse 2 stylh1. none 3 indent20px

Scope

...

The functions for terminating task processes by the JobScheduler Master and Universal Agent have been extended allow the use of

...

SIGTERM

...

on Unix servers

...

in addition to SIGKILL and allows an orderly of termination of task processes to take place over a limited period of time.

...

Feature History

This feature was introduced with has been implemented stepwise between Release 1.9.0 and 1.10.0 (see the table of issues below for more detailed information).

Issues

Support of this feature is subject to the following issues:

...

• Welche Rolle ist für den Fall verantwortlich? Wer will etwas? Engineering, Operating, Business
• Was ist das Ziel? Was ist das Mittel? Was ist die Motivation?

Implementation

• Wie ist die Lösung implementiert? Mit welchen Mitteln?

...

The information contained in this article draws together detailed information contained in a range of issues and should primarily be of interest to persons in engineering and to a lesser extent persons in operating functions.

Implementation

• The use of both SIGTERM and SIGKILL 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 after the the kill command has been issued.

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

  • The post-processing methods 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 the SIGKILL 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).

JobScheduler Commands

The following operations can be carried out from the JobScheduler Operating Center interface (JOC):

1. Operation: kill immediately
   • JOC sends <kill_task immediately="yes"/>
   • The process is killed immediately using the SIGKILL signal.
2. Operation: terminate with timeout
   • JOC sends <kill_task immediately="yes" timeout="15"/>
   • The process receives a SIGTERM signal. Should that process not terminate within the specified timeout period then it will be killed with a SIGKILL signal.
3. Operation: terminate
   • JOC sends <kill_task immediately="yes" timeout="never"/>
   • The respective process receives a SIGTERM signal. No monitoring of the termination of that process as in operation 2) is performed.
   • The process receives a SIGTERM signal. Monitoring of the process termination as described in operation 2. is not carried out.

Delimitation

...

• This feature is intended for Unix platforms that implement the SIGTERM and SIGKILL signals. It is not intended for Windows platforms for which exclusively the Kill Immediately command applies.
• When using traps then please consider that the process created by the <shell> element receives the signal. Subsequent scripts that are called within the <shell> element will not receive the signal.
  You could therefore:
  • configure traps directly within the <shell> element. The shell process will then receive and handle the signal.
  • configure traps in a shell script that is added by an <include> element instead of being stated within the <shell> element. The included shell script will receive and handle the signal.
  • forward signals to subsequent shell scripts that are called within a <shell> element.

...