Reliable management of signal SIGPIPE and SIGTERM Post: 302406226

9 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. AIX

auditing fails with SIGPIPE signal on 1/4 hour

Hi folks, Can anyone assist with pointers for the following snag? We have custom method (IBM-supplied) for running the audit subsystem on 5.1-07 /etc/security/audit objects, events and config have been edited, and the /etc/security/audit/streamcmds contains the following routine; ...

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

4. Programming

Catch signal SIGPIPE print errno but it's value equal to 2

catch signal SIGPIPE ,print errno but it's value equal to 2(ENOENT) #define ENOENT 2 /* No such file or directory */ is it should be EPIPE ? #define EPIPE 32 /* Broken pipe */ Thanks !

5. UNIX for Advanced & Expert Users

Why not SIGPIPE for readers of pipe/FIFO?

Hi This is a exercise question from Unix network programming vol2. Why the SIGPIPE signal is generated only for writers when readers disappear. why not it is generated for readers when writer disappears. I guess, if the writer didn't get any response like the reader gets EOF, it will...

6. Programming

SIGPIPE and EPIPE

When a write() writes on a broken pipe, with no readers, it generates a SIGPIPE signal and the process exits. When the write() returns -1 and errno is EPIPE? Do I have an handler for SIGPIPE, or can I ignore it?

7. UNIX for Dummies Questions & Answers

Is this website reliable ?

edit by bakunin: content not relevant for our site (and bordering on spam) SNIPped, thread closed. My suggestion is to - before even considering to buy anything online - put more effort in research, i.e. what the web site you write a comment at, is all about. This one here is definitely not for...

8. Homework & Coursework Questions

C TCP/IP Reliable Transmission project not reliable

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: We must do the following for a massive coding project that is due at 12:20PM on Monday, July 22, 2013. We are to...

9. AIX

SIGTERM failing in AIX

I have 2 AIX 6.1 systems running on PowerPCs - production and .. .everything else. :p . Until the installation of a TLS certificate in an application, some copying of files ("cloning an environment") and upgrading a listener, sending a kill -15 worked on any script/application, so long as we were...

LEARN ABOUT OSF1

pthread_kill

pthread_kill(3) 					     Library Functions Manual						   pthread_kill(3)

NAME

       pthread_kill - Delivers a signal to a specified thread. (This routine is available only on a UNIX system.)

LIBRARY

       DECthreads POSIX 1003.1c Library (libpthread.so)

SYNOPSIS

       #include <pthread.h> #include <signal.h>

       int   pthread_kill(
			   pthread_t   thread,
			   int	       sig);

STANDARDS

       Interfaces documented on this reference page conform to industry standards as follows:

       IEEE Std 1003.1c-1995, POSIX System Application Program Interface

PARAMETERS

       Thread to receive a signal request.  A signal request.

DESCRIPTION

       This  routine sends a signal to the specified target thread thread.  Any signal defined to stop, continue, or terminate will stop or termi-
       nate the process, even though it can be handled by the thread.  For example, SIGTERM terminates all threads in the process, even though	it
       can be handled by the target thread.

       Specifying a sig argument of zero (0) causes this routine to validate the thread argument but not to deliver any signal.

       The name of the "kill" routine is sometimes misleading, because many signals do not terminate a thread.

       The  various  signals  are  as follows: SIGHUP, SIGPIPE, SIGTTIN SIGINT, SIGALRM, SIGTTOU SIGQUIT, SIGTERM, SIGIO SIGTRAP, SIGUSR1, SIGXCPU
       SIGABRT, SIGSYS, SIGXFSZ SIGEMT, SIGURG, SIGVTALRM SIGFPE, SIGSTOP, SIGPROF SIGKILL, SIGTSTP, SIGINFO  SIGBUS,  SIGCONT,  SIGUSR1  SIGSEGV,
       SIGCHLD, SIGUSR2

       If this routine does not execute successfully, no signal is sent.

RETURN VALUES

       If  an  error condition occurs, this routine returns an integer value indicating the type of error.  Possible return values are as follows:
       Successful completion.  The value of sig is invalid or unsupported signal value.  The value of thread does not specify an existing thread.

ERRORS

       None

RELATED INFORMATION

       Manuals: Guide to DECthreads and Programmer's Guide

       delim off

																   pthread_kill(3)