Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.programmer
Subject: Re: pause(2) vs. sigpause(3)
Message-ID: <27817:Oct3104:58:4990@kramden.acf.nyu.edu>
Date: 31 Oct 90 04:58:49 GMT
References: <43321@eerie.acsu.Buffalo.EDU> <717@inews.intel.com>
Organization: IR
Lines: 14

In article <717@inews.intel.com> bhoughto@cmdnfs.intel.com (Blair P. Houghton) writes:
> Why obsoleted a perfectly simple system call with a
> library function?

Here it's pause(3) and sigpause(2). What machine are you using?

> (BTW, neither of them is ANSI C; I don't know which might
> be in POSIX).

POSIX imitated the BSD signal facilities, with some helpful additions.
It made sigpause() into sigsuspend(). The difference is that the
argument is a ``sigset_t'' manipulated by macros.

---Dan