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
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
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
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 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
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
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
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
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
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
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
cssd(1M) System Administration Commands cssd(1M)
NAME
cssd - daemon which invokes and watches the CSs
SYNOPSIS
/usr/sbin/cssd [-f filename]
AVAILABILITY
SUNWjfpu
DESCRIPTION
cssd is the command which invokes and watches CS available in MLE (Multi Language Environment). After five seconds of the ending (includ-
ing abnormal termination) of a CS, cssd re-invokes the CS.
CS STARTING INFORMATION FILE
In a CS starting information file, /etc/css.conf by default, some CS starting information directories are described. This file can be cus-
tomized. cssd reads /etc/css.conf to get CS starting information directories, and then it invokes all executable files in the directories.
Usually, each CS itself is not placed in the directories and is invoked indirectly from a script in one of the directories.
CS STARTING SCRIPT
A CS starting script is located in a CS starting information directory. cssd reads all CS starting information directories in the sequence
specified in /etc/css.conf and finds to invoke all CS starting scripts. If two or more scripts which have the same filename are found,
cssd invokes only the first one.
UPDATING CS STARTING INFORMAION
When cssd receives signal SIGHUP , it re-reads /etc/css.conf and re-finds all CS starting scripts, and then restarts, starts or terminates
each script according to the following conditions.
A script whose modified time is changed (is to be restarted) A script which is newly added (is to be started) A script which is
deleted (is to be terminated)
TO TERMINATE
When cssd receives signal SIGTERM, it sends SIGTERM to each CS under the cssd's management and terminates itself (in general, each CS also
terminates with the signal).
ERROR INFORMATION
As a facility of daemon, cssd sends error information at level `err' , and invoke/re-invoke information at level `notice' to syslogd(1M).
OPTION
-f filenaSpecify a CS starting information file. Without this option, /etc/css.conf is used.
FILE
/etc/css.conf file for the information of CSs by default
SEE ALSO
css.conf(4), syslogd(1M)
BUGS
If a CS starting script is programmed so that itself is exec-ed by a CS, cssd understands that the process of the CS starting script is
terminated in spite of the CS's termination, and so puts syslog message out.
SunOS 5.10 10 Jan 2003 cssd(1M)