Sponsored Content
Full Discussion: SIGSTOP and SIGKILL
Top Forums Shell Programming and Scripting SIGSTOP and SIGKILL Post 302497729 by alister on Thursday 17th of February 2011 11:19:11 PM
Old 02-18-2011
SIGHUP is sent to processes when their controlling terminal is closed. You may be interested in reading the nohup(1) man page if you'd like a process to ignore that signal.

Regards,
Alister

Last edited by alister; 02-18-2011 at 12:25 AM..
This User Gave Thanks to alister For This Post:
 

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Why SIGKILL will occur?

Hi Gurus, I am executing my Datastage jobs on UNIX operating System. While running the jobs i am getting the following error: main_program: Unexpected termination by Unix signal 9(SIGKILL) Can any one please let me know what are the possible situations where this SIGKILL will arrise? ... (9 Replies)
Discussion started by: choppas
9 Replies

2. 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

3. Solaris

SIGQUIT and SIGKILL message

Dear All, I have machine with SunOS 5.10 Generic_138888-01 sun4v sparc SUNW,SPARC-Enterprise-T5120. Yesterday there is something at dmesg command : May 25 18:09:02 cacao_launcher: Timeout occured on heartbeat channel, cleanup engaged May 25 18:09:07 cacao_launcher: watchdog : warning,... (0 Replies)
Discussion started by: mbah_jiman
0 Replies

4. 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
EXIT(2) 						      BSD System Calls Manual							   EXIT(2)

NAME
_exit -- terminate the calling process LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <unistd.h> void _exit(int status); DESCRIPTION
The _exit() system call terminates a process with the following consequences: o All of the descriptors open in the calling process are closed. This may entail delays, for example, waiting for output to drain; a process in this state may not be killed, as it is already dying. o If the parent process of the calling process has an outstanding wait(2) call or catches the SIGCHLD signal, it is notified of the calling process's termination and the status is set as defined by wait(2). o The parent process-ID of all of the calling process's existing child processes are set to 1; the initialization process inherits each of these processes (see init(8) and the DEFINITIONS section of intro(2)). o If the termination of the process causes any process group to become orphaned (usually because the parents of all members of the group have now exited; see ``orphaned process group'' in intro(2)), and if any member of the orphaned group is stopped, the SIGHUP signal and the SIGCONT signal are sent to all members of the newly-orphaned process group. o If the process is a controlling process (see intro(2)), the SIGHUP signal is sent to the foreground process group of the controlling ter- minal, and all current access to the controlling terminal is revoked. Most C programs call the library routine exit(3), which flushes buffers, closes streams, unlinks temporary files, etc., before calling _exit(). RETURN VALUES
The _exit() system call can never return. SEE ALSO
fork(2), sigaction(2), wait(2), exit(3), init(8) STANDARDS
The _exit() system call is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1''). HISTORY
The _exit() function appeared in Version 7 AT&T UNIX. BSD
June 4, 1993 BSD
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy