HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

351

352

353

354

355

356

357

358

359

360

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man2/!!!intro.2

________________________________________________________________

___ ___

sigaction(2) sigaction(2)

signals are discarded regardless of whether the signal is blocked by any of the threads.

For more information regarding signalsand threads, see signal(5).

FUTURE DIRECTIONS

The fpathconf() function is marked as an extension in the list of safe functions because it is not

included in the corresponding list in the ISO POSIX-1 standard, but it is expected to be added in a future

revision of that standard.

SEE ALSO

kill(2), setjmp(3C), sigaltstack(2), signal(2), sigprocmask(2), sigqueue(2), sigsetops(3C), sigsuspend(2),

wait(2), waitid(2), <signal.h>, <ucontext.h>.

CHANGE HISTORY

First released in Issue 3.

Entry included for alignment with the POSIX.1-1988 standard.

Issue 4

The following changes are incorporated for alignment with the ISO POSIX-1 standard:

• The type of argument act is changed from struct sigaction * to const struct sigac-

tion *

• A statement is added to the DESCRIPTION section indicating that the consequence of attempting

to set SIG_DFL for a signal that cannot be caught or ignored is unspeciﬁed. The EINVAL

error,

describing one possible reaction to this condition, is added to the ERRORS section.

Other changes are incorporated as follows:

• The

raise() and signal() functions are added to the list of functions that are either reen-

trant or not interruptible by signals;

fpathconf() is also added to this list and marked as an

extension;

ustat() is removed from the list, as this function is withdrawn from the interface

deﬁnition. It is no longer speciﬁed whether abort(), chroot(), exit(), and

longjmp()

also fall into this category of functions.

• The APPLICATION USAGE section is added. Most of this text is moved from the DESCRIPTION

SECTION in Issue 3.

• The FUTURE DIRECTIONS section is added.

Issue 4, Version 2

The following changes are incorporated for X/OPEN UNIX conformance:

• The DESCRIPTION describes sa_sigaction , the member of the sigaction structure that is the

signal-catching function.

• The DESCRIPTION describes the SA_ONSTACK, SA_RESETHAND, SA_RESTART,

SA_SIGINFO, SA_NOCLDWAIT , and SA_NODEFER settings of sa_ﬂags. The text describes the

implications of the use of SA_SIGINFO for the number of arguments passed to the signal-catching

function. The text also describes the effects of the SA_NODEFER and SA_RESETHAND ﬂags on

the delivery of a signal and on the permanence of an installed action.

• The DESCRIPTION speciﬁes the effect if the action for the

SIGCHLD signal is set to

SIG_IGN.

• In the DESCRIPTION, additionaltext describes the effect if the action is a pointer to a function. A

new bullet covers the case where

SA_SIGINFO is set. SIGBUS is given as an additional signal

for which the behaviour of a process is undeﬁned following a normal return from the signal-

catching function.

• The APPLICATION USAGE section is updated to describe use of an alternate signal stack;

resumption of the process receiving the signal; coding for compatibility with POSIX.4-1993; and

implementation of signal-handling functions in BSD.

HP-UX Release 11i: December 2000 − 7 − Section 2−−339

___