Skip to contentSkip to conversation

Question about Linux signal handling

DISCUSSION Tom Sanders 2 participants 2 messages Feb 23, 2003

lore
Share & tools
lore
#0 lore raw

If I catch a signal (SIGUSR2) using "sigaction" call then is the signal handler replaced with default handling, if I don't install the signal handler again?

I remember that in UNIX "signal" system call default signal bahavior was to replace the signal handler with default after everytime signal was received?

My observation is that even if I get same signal twice, I get the same print (which I have in my signal handler) again, illustrating that signal handler was not replaced with default !!! Is that the correct behavior of "sigaction"?

Thanks,
Tom

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

#1 lore raw
Quoted 8 lines · Tom Sanders

If I catch a signal (SIGUSR2) using "sigaction" call then is the signal handler replaced with default handling, if I don't install the signal handler again?

I remember that in UNIX "signal" system call default signal bahavior was to replace the signal handler with default after everytime signal was received?

Quoted 5 lines

My observation is that even if I get same signal twice, I get the same print (which I have in my signal handler) again, illustrating that signal handler was not replaced with default !!! Is that the correct behavior of "sigaction"?

Depends on the value of sa_flags parameter:

Quoted 1 line

From the manpage SIGACTION(2):

sa_flags specifies a set of flags which modify the behaviour of the signal handling process. It is formed by the bitwise OR of zero or more of the following:

SA_NOCLDSTOP
If signum is SIGCHLD, do not receive notifi- cation when child processes stop (i.e., when child processes receive one of SIGSTOP, SIGTSTP, SIGTTIN or SIGTTOU).

SA_ONESHOT or SA_RESETHAND
Restore the signal action to the default state once the signal handler has been
called. (This is the default behavior of
the signal(2) system call.)

SA_RESTART
Provide behaviour compatible with BSD signal semantics by making certain system calls restartable across signals.

SA_NOMASK or SA_NODEFER
Do not prevent the signal from being
received from within its own signal handler.

SA_SIGINFO
The signal handler takes 3 arguments, not
one. In this case, sa_sigaction should be
set instead of sa_handler. (The sa_sigac-
tion field was added in Linux 2.1.86.)

You are describing SA_ONESHOT as what you think you should get..

I believe you are getting the correct result. With the ONESHOT option you can/will loose signals, since the handler would be set back to the default, and any subsequent signal lost. This loss of signals is one of the original complaints about UNIX signal handling.

Now my manpage continues with the warning:

The POSIX spec only defines SA_NOCLDSTOP. Use of other sa_flags is non-portable.

and:

CONFORMING TO
POSIX, SVr4. SVr4 does not document the EINTR condition.