Losing signal problem Post: 302578786

10 More Discussions You Might Find Interesting

1. Programming

[Problem] raise a signal in FreeBSD

I am trying to send a SIGUSR1 to a set of process. Please tell me how to do. I've tried the system call raise(int sig) but it just raise a signal of to the 'current process.' My program is about a network chat server. When a client connects in, The main process will fork a new process...

2. UNIX for Advanced & Expert Users

I have a problem using signal SIGUSR2

hi I have created a application which uses SIGUSR2. It send this signal to server and waits for signal SIGUSR2 from server after server performing some operation server sends SIGUSR2 back to the application. The application then quits. This works fine which ran from terminal , but when I...

3. Programming

Signal Problem

I am using the signal function, and passing it a function named quit procedure...I get the following warning.... passing arg2 of signal from incompatible pointer type... void quit_procedure(void); //this is the way i define my prototype... signal(SIGINT, quit_procedure); Please guide...

4. Programming

problem with signal()

#include<signal.h> void suicide(); main() { printf("use CTRL \\ for exiting \n"); //signal(SIGINT,SIG_DFL); signal(SIGQUIT,suicide); for (;;); } void suicide() { printf("hello here you r in the suicide code "); } i was just starting with signals .. and tried this ,, but in the...

5. Programming

Problem with signal handler and interrupted system call

Hi, I have a daq program that runs in an infinite loop until it receives SIGINT. A handler catches the signal and sets a flag to stop the while loop. After the loop some things have to be cleaned up. The problem is that I want my main while loop to wait until the next full second begins, to...

6. Programming

problem in SIGSEGV signal handling

i wrote handler for sigsegv such that i can allocate memory for a variable to which sigsegv generated for illlegal acces of memory. my code is #include <signal.h> #include<stdio.h> #include<stdlib.h> #include<string.h> char *j; void segv_handler(int dummy) { j=(char *)malloc(10); ...

7. Programming

problem in reforking and signal handling

hi friends i have a problem in signal handling ... let me explain my problem clearly.. i have four process .. main process forks two child process and each child process again forks another new process respectively... the problem is whenever i kill the child process it is reforking and the...

8. Programming

UNIX signal problem

Hi all, Sorry about the title,at first i decided to ask a problem about the signal mechanism,however,i'm now figured it out.Sorry to forget modify the title:wall:.I had a small problem that if i use the code which is commented,the code would get a segment fault,while the above code NOT.what's...

9. Programming

problem in doing coding of signal handler

i m unble to execute code of signal handler using a) Wait b) Waitpid

10. Linux

Problem with dovecot (Killed with signal 15)

hey, i have been facing a very fatel error with dovecot.. i am getting this error in my dovecot.log file dovecot: Feb 13 15:21:02 Fatal: chdir(/var/mail/folders/user1) failed with uid 1001: Permission denied dovecot: Feb 13 15:21:02 Error: child 18732 (imap) returned error 89 dovecot: Feb...

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)

10 More Discussions You Might Find Interesting

1. Programming

[Problem] raise a signal in FreeBSD

Discussion started by: Namely

2. UNIX for Advanced & Expert Users

I have a problem using signal SIGUSR2

Discussion started by: khan_069

3. Programming

Signal Problem

Discussion started by: jacques83

4. Programming

problem with signal()

Discussion started by: narendra.pant