06-08-2017
I presume that:
- the script that you showed us that you're trying to kill is not the actual code that you're trying to kill,
- that you are not the author of the code you're trying to kill (since you didn't know the trap was there), and
- that you didn't consult with the author of that script before trying to write code to kill it
.
One obvious reason why someone would add a
trap command to ignore signals to a script that is expected to run for a while (i.e., more than a 1 instruction cycle) would be to keep scripts like yours from randomly killing them. Trying to ignore SIGSTOP and SIGKILL produces undefined results, but it is certainly a reasonable first attempt to keep a script running while the author of that script tracks down why their script is being terminated for no obvious reason.
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
LEARN ABOUT DEBIAN
cgi-fcgi
cgi-fcgi(1) General Commands Manual cgi-fcgi(1)
NAME
cgi-fcgi - bridge from CGI to FastCGI
SYNOPSIS
cgi-fcgi -f cmdPath
cgi-fcgi -bind -connect connName
cgi-fcgi -start -connect connName appPath [nServers]
cgi-fcgi -connect connName appPath [nServers]
DESCRIPTION
cgi-fcgi is a CGI/1.1 program that communicates with an already-running FastCGI application in order to respond to an HTTP request. cgi-
fcgi is also capable of starting a FastCGI application.
When you invoke cgi-fcgi as
cgi-fcgi -f cmdPath
then cgi-fcgi opens the file at cmdPath and reads its arguments from that file. cgi-fcgi will skip lines that begin with the comment char-
acter #. The first non-comment line should contain valid arguments in one of the other three forms.
The -f form of cgi-fcgi is designed for Unix systems whose exec(2) family of system calls supports the execution of command interpreter
files. For instance, if a file with execute permission contains the text
#! /bin/cgi-fcgi -f
-connect /httpd/root/sock/app /httpd/root/bin/app
the effect is the same as executing
/usr/bin/cgi-fcgi -connect /httpd/root/sock/app /httpd/root/bin/app
When you invoke cgi-fcgi as
cgi-fcgi -bind -connect connName
the connName argument is either the path name of a Unix domain listening socket or a host:port pair. If connName contains a colon, it is
assumed to be host:port. cgi-fcgi performs a connect(2) using connName. If the connect succeeds, cgi-fcgi forwards the CGI environment
variables and stdin data to the FastCGI application, and forwards the stdout and stderr data from the application to cgi-fcgi's stdout
(most likely connected to a Web server). When the FastCGI application signals the end of its response, cgi-fcgi flushes its buffers and
exits, and the Web server completes the http response.
When you invoke cgi-fcgi as
cgi-fcgi -start -connect connName appPath [nServers]
then cgi-fcgi performs the function of starting one or more FastCGI application processes. The connName argument specifies either the path
name of the Unix domain listening socket that cgi-fcgi will create, or is "localhost:NNN" where NNN is the port number of the TCP/IP lis-
tening socket that cgi-fcgi will create on the local machine. (cgi-fcgi will not create processes on remote machines.) After cgi-fcgi
creates the listening socket, it forks nServers copies of a process running the executable file appPath. If nServers is omitted, the
effect is as if the value "1" had been specified. The processes share the single listening socket.
When you invoke cgi-fcgi as
cgi-fcgi -connect connName appPath [nServers]
cgi-fcgi performs -bind and then, if necssary, performs -start and repeats the -bind. That is, cgi-fcgi first operates as if the command
had been
cgi-fcgi -bind -connect connName
If the connect fails, cgi-fcgi tries
cgi-fcgi -start -connect connName appPath [nServers]
and finally retries
cgi-fcgi -bind -connect connName
In this form, cgi-fcgi does not support TCP/IP connections.
ENVIRONMENT VARIABLES
The usual CGI ones, but they are not interpreted by cgi-fcgi.
SEE ALSO
FGCI_accept(3).
(in Debian, /usr/share/doc/libfcgi?/*)
BUGS
cgi-fcgi doesn't generate useful HTTP responses in case of error, and it generates no response at all when run as start-fcgi.
On Digital UNIX 3.0 systems the implementation of Unix Domain sockets does not work when such sockets are stored on NFS file systems.
Symptom: cgi-fcgi may core dump or may exit with status 38. Work-around: store sockets in local file systems (/tmp often works) or use
TCP/IP.
On AIX systems the implementation of listening sockets does not support socket sharing, and the standard FastCGI application libraries
can't synchronize access to AIX listening sockets. Work-around: Don't use the nServers argument on AIX.
HISTORY
Copyright (c) 1996 Open Market, Inc. See the file "LICENSE.TERMS" for information on usage and redistribution of this file, and for a DIS-
CLAIMER OF ALL WARRANTIES. $Id: cgi-fcgi.1,v 1.1.1.1 1997/09/16 15:36:26 stanleyg Exp $
1997-09-17 cgi-fcgi(1)