Sponsored Content
Full Discussion: SIGTERM failing in AIX
Operating Systems AIX SIGTERM failing in AIX Post 302998800 by jim mcnamara on Wednesday 7th of June 2017 02:53:13 PM
Old 06-07-2017
As far as I am aware there is no problem with SIGTERM on AIX compared to any other other standards compliant UNIX. Any signal can optionally be blocked, except SIGSTOP and SIGKILL.

There has to be a login/startup/setup script that is blocking SIGTERM. I don't have magic suggestions. But what you describe is not standard out of the box behavior.

I would start by checking the usual suspects like profile scripts and login scripts.
Other regulars here on the forums have a lot of detailed AIX knowledge, hopefully they have an explanation or a strategy to help.
 

10 More Discussions You Might Find Interesting

1. Programming

signals - SIGTERM

Hi all, I need some urgent help. we are using Dynix/ptx V4.5 on i386, have several processes and instances are running on the box round the clock.we increased the processes recently. We have coded to handle the signals in our programs. Recently, we noticed most of our processes are... (2 Replies)
Discussion started by: reddyb
2 Replies

2. HP-UX

make fuser send SIGTERM?

Hello, Nice forum BTW... anyway on to my question. I am trying to write a korn shell script that will shut down a java VM. The first challenge was how to figure out which java VM to kill, as there can be other java processes running at the same time. Then I discovered fuser. It says it... (4 Replies)
Discussion started by: adamides
4 Replies

3. Programming

How to implement SIGKILL and SIGTERM and print a message?

Hello, I am running a webserver that uses sockets, forks, and children. The parent process listens for connections and the child processes the information. I am trying to figure out why the code I have below SIGTERM, and SIGKILL never fire. I was messing around with the printfs and doesnt... (11 Replies)
Discussion started by: norelco55
11 Replies

4. Programming

the parent receive SIGTERM from its child (httpd) ?

the parent is a process manager in our design, and httpd service is one of its child processes, which is started in foreground mode (with "-D FOREGROUND" options) according to our requirements. when httpd service is started, one main httpd process and eight sub httpd processes can be found by... (4 Replies)
Discussion started by: aaronwong
4 Replies

5. Shell Programming and Scripting

How to detect SIGTERM,SIGKILL signal in UNIX

Dear All We have JBOSS server running on Linux we need to track Graceful Shutdown(SIGTERM) and Forceful Shutdown(SIGKILL) timestamp and write it into one file, I am new to UNIX Signal processing if is it possible how to detect it? We generally do $kill PID For Graceful... (5 Replies)
Discussion started by: mnmonu
5 Replies

6. Programming

Reliable management of signal SIGPIPE and SIGTERM

I' m note very expert in the reliable manage of signal... but in my server I must manage SIGPIPE for the socket and SIGTERM... I've wrote this but there is something wrong... Can someone explain me with some example the reliable management of signal?? This is what I've wrote in the server ... (2 Replies)
Discussion started by: italian_boy
2 Replies

7. AIX

FIREFOX Failing in AIX

Hi Guys, I tried running the firefox in AIX 6.1 and got the below error.. -bash-3.00# firefox Could not load program /usr/mozilla/firefox/firefox-bin: Could not load module /usr/mozilla/firefox/libxul.so. Dependent module /usr/lib/libgtk-x11-2.0.a(libgtk-x11-2.0.so.0) could not... (0 Replies)
Discussion started by: kkeng808
0 Replies

8. Shell Programming and Scripting

Current instance of Shell ignoring SIGTERM

Hello. Could anyone tell me how can I configure a instance of Shell to ignore the SIGTERM signal? I would really appreciate. Thanks. (6 Replies)
Discussion started by: razolo13
6 Replies

9. Shell Programming and Scripting

ksh child process not ignoring SIGTERM

My ksh version is ksh93- =>rpm -qa | grep ksh ksh-20100621-3.fc13.i686 I have a simple script which is as below - #cat test_sigterm.sh - #!/bin/ksh trap 'echo "removing"' QUIT while read line do sleep 20 done I am Executing the script From Terminal 1 - 1. The ksh is started... (3 Replies)
Discussion started by: rpoornar
3 Replies

10. AIX

Failing to add new NetApp disk AIX 7.1 - but no error

Hello, AIX 7.1 - several NetApp disks already running. Trying to install a new one. Storage folks provision it. I run cfgmgr - nothing. no new disks show up in "lsdev", "sanlun lun show" shows no new device. No errors, just nothing. Storage guys disconnect it and attaches to another aix server -... (5 Replies)
Discussion started by: sid
5 Replies
kill(1) 						      General Commands Manual							   kill(1)

NAME
kill - Sends a signal to a running process SYNOPSIS
kill -l [exit_status] kill [-signal_name | signal_number] process_ID... kill -s signal_name process_ID... Note The C shell has a built-in version of the kill command. If you are using the C shell, and want to guarantee that you are using the command described here, you must specify the full path /usr/bin/kill. See the csh(1) reference page for a description of the built-in command. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: kill: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
The kill command supports the following options: Lists signal names. If you specify an exit status (a numeric value) or the shell special parameter $?, which expands to the exit status of the most recent pipeline, kill prints the name of the terminating signal. Specifies the signal to send, using one of the symbolic names defined for required signals or job control signals. Values of signal_name are recognized in both uppercase or lowercase letters, and without the SIG prefix. The symbolic name 0 (zero), which represents the value 0 (zero), is also recognized. The corresponding signal is sent instead of SIGTERM. Specifies the signal to send to the process. You can specify either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal names and numbers, see the sigaction() system call. OPERANDS
A process identification number [Tru64 UNIX] There are several special process identification numbers (PIDs) that you can specify to cause the following special actions: The signal is sent to all processes having a process group ID equal to the process group ID of the sender, except those with a process ID of 0 (zero) and the process ID of the init process. If the effective user ID of the sender is not 0 (root), the signal is sent to all processes with a process group ID equal to the effective user ID of the sender, except those with a process ID of 0 (zero) and the process ID of the init process. If the effective user ID of the sender is 0 (root), the signal is sent to all processes, except the process ID of 0 (zero) and the process ID of the init process. The signal is sent to all processes whose process group number is equal to the absolute value of PID. Note that when you specify any negative PID, you must also specify the signal to be sent, even the default signal SIGTERM. A decimal integer specifying a signal number or the exit status of a process terminated by a signal. DESCRIPTION
The kill command sends a signal to one or more running processes. The default is the SIGTERM signal (signal number 15), which usually ter- minates processes that do not ignore or catch the signal. You identify the process to be signaled by specifying its process identification number (also known as the process ID or PID). The shell displays the PID of each process that is running in the background or, if you start more than one process in a pipeline, the shell displays the number of the last process. You can also use the ps command to display PIDs. [Tru64 UNIX] The name of the kill command is misleading because many signals, including SIGUSR1, do not terminate processes. [Tru64 UNIX] Unless you are operating with superuser privileges, the process you wish to signal must belong to you. When operating with superuser authority, you can signal any process. [Tru64 UNIX] See the kill() system call for a complete discussion of kill. Note that the csh command contains a built-in subcommand named kill, but the command and subcommand do not necessarily work in the same way. For information on the subcommand, see csh. NOTES
Some applications and scripts depend on the process ID of the init program being 1 (one): do not depend on it. Instead, use standard methods, such as the ps and grep commands, to obtain all process IDs. EXIT STATUS
The following exit values are returned: At least one matching process was found, and the specified signal was successfully processed for at least one matching process. An error occurred. EXAMPLES
The following command terminates the process with the specified PID: kill 1095 This command terminates process 1095 by sending it the default SIGTERM signal. Note that process 1095 might not actually terminate if it has made special arrangements to ignore or catch the SIGTERM signal. The following command terminates several processes that ignore the default signal: kill -KILL 17285 15692 This command sends SIGKILL to processes 17285 and 15692. The SIGKILL signal usually cannot be ignored or caught. The following com- mand terminates all of your background processes: kill 0 This command sends the SIGTERM signal to all members of the shell process group. This includes all background processes started with &. Although the signal is sent to the shell, it has no effect because the shell ignores the default signal 15. The following com- mand terminates all of your processes and logs you out: kill -KILL 0 This command sends SIGKILL to all members of the shell process group. Because the shell cannot ignore SIGKILL, this also terminates the login shell and logs you out. If you are using multiple windows, this closes the active window. The following command terminate all the processes that you own: kill -KILL -1 This command sends SIGKILL to all the processes that you own, even those that belong to other process groups. If you are using mul- tiple windows, this command closes all the windows. The following command sends a specific signal to a specific process: kill -USR1 1103 This command sends the SIGUSR1 signal to process 1103. The action taken on the SIGUSR1 signal is defined by the particular applica- tion you are running. The following command lists the signal names in numerical order, stripped of the SIG prefix: kill -l 1) HUP 13) PIPE 25) XFSZ 37) RTMIN+4 2) INT 14) ALRM 26) VTALRM 38) RTMIN+5 3) QUIT 15) TERM 27) PROF 39) RTMIN+6 4) ILL 16) URG 28) WINCH 40) RTMIN+7 5) TRAP 17) STOP 29) PWR 41) RTMAX-7 6) LOST 18) TSTP 30) USR1 42) RTMAX-6 7) EMT 19) CONT 31) USR2 43) RTMAX-5 8) FPE 20) CHLD 32) RESV 44) RTMAX-4 9) KILL 21) TTIN 33) RTMIN 45) RTMAX-3 10) BUS 22) TTOU 34) RTMIN+1 46) RTMAX-2 11) SEGV 23) POLL 35) RTMIN+2 47) RTMAX-1 12) SYS 24) XCPU 36) RTMIN+3 48) RTMAX The command output can vary from system to system. ENVIRONMENT VARIABLES
The following environment variables affect the execution of kill: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. FILES
Specifies signal names. SEE ALSO
Commands: csh(1), killall(8), ksh(1), ps(1), Bourne shell sh(1b), POSIX shell sh(1p) Functions: kill(2), sigaction(2) Standards: standards(5) kill(1)
All times are GMT -4. The time now is 09:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy