Term signal for UNIX Job

5 votes

Basically, it's about having the ability to cancel a running Linux job from the Enterprise Manager so that it does not receive a KILL signal but a different, configurable signal (eg HUP or TERM).

A simple solution would be to make the signal to be used in the option "Kill" configurable.

Better would be a separate option "Signal / Terminate" with a configurable signal (in addition to the existing option "Kill" with a fixed signal KILL). With this additional option, OpCon should send a configurable signal to the Linux job and wait for what happens.

This Idea Comes form Philip Warenits ITSV

Collecting community feedback UNIX/Linux Agent Suggested by: Hidden identity (26 Jul, '19) • Upvoted: 16 Feb, '22 • Comments: 1

Comments: 1

16 Feb, '22
Roger Zwick
Generali-DE/Badenia needs this feature, too. Normally a SIGTERM 9 (Kill -9) is used for the job kill.
If Badenia uses a job kill command in the EM for a Linux Job, then the whole process tree is not cleaned up.
When a job starts a subjob against the database, the database connection remains.

The database connection then remains until the specified timeout of the database terminates the process (currently 15 minutes).

Currently, Badenia must send a kill -15 on the Linux machine itself.

It would be good if for example in the config of the UNIX LSAM the kill can be defined (kill -9 or kill -15). It would be even nicer if it were possible to choose between the different job kill functions in the user interface for Unix jobs.