sigpause(2) Mac OS X Developer Tools Manual Page

Mac Dev Center Mac OS X Reference Library General Mac OS X Man Pages

This manual page is part of Xcode Tools version 3.2.2

To obtain these tools:

Install the Xcode Tools from developer.apple.com.

If you are running a version of Xcode Tools other than 3.2.2, view the documentation locally:

In Xcode
In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

For more information about the manual page format, see the manual page for manpages(5).
For more information about this technology, look for other documentation in the Apple Reference Library.
For general information about writing shell scripts, read Shell Scripting Primer.


SIGPAUSE(2)                                BSD System Calls Manual                               SIGPAUSE(2)

NAME
     sigpause -- atomically release blocked signals and wait for interrupt

LIBRARY
     Standard C Library (libc, -lc)

SYNOPSIS
     #include <signal.h>

     int
     sigpause(int sig);

DESCRIPTION
     This interface is made obsolete by sigsuspend(2).

     Sigpause() assigns sig to the set of masked signals and then waits for a signal to arrive; on return
     the set of masked signals is restored.  Sig is usually 0, indicating that no signals are to be blocked.
     Sigpause() always terminates by being interrupted, returning -1 with errno set to EINTR.

COMPATIBILITY
     sigpause() now takes a signal value and not a mask.  This often appears as a hang in sigpause$UNIX2003
     or with sigpause() returning with errno set to EINVAL.  Use sigsuspend() with signal masks.

SEE ALSO
     kill(2), sigaction(2), sigblock(2), sigprocmask(2), sigsuspend(2), sigvec(2)

HISTORY
     The sigpause() function call appeared in 4.2BSD and has been deprecated.

BSD                                             June 2, 1993                                             BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors: Report errors in the content of this documentation with the feedback links below.
Bug reports: Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems: Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you?