Xref: utzoo comp.unix.questions:31251 comp.unix.wizards:25557
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: talk session
Message-ID: <7766@auspex.auspex.com>
Date: 12 May 91 20:15:11 GMT
References: <azK/EJXR7ndok@idunno.Princeton.EDU> <1489@cvbnetPrime.COM> <1991May9.161406.21802@hal.com>
Followup-To: comp.unix.questions
Organization: Auspex Systems, Santa Clara
Lines: 19

>:Actually usleep(3) is going away in System V Release 4 (SVr4)
>:so you can use select(2):
>
>Am I missing something here, or why can't you just make a usleep out
>of setitimer?  You could even use ITIMER_REAL.

Funny, that's just what Berkeley did when they did "usleep()" in the
first place....

And yes, you could do that in S5R4; in fact, that's probably what the
"usleep()" in the BSD compatibility package in S5R4 (see "UNIX(R) System
V Release 4 BSD/XENIX(R) Compatibility Guide) does (in fact, they may
well just have lifted the BSD code...).

I don't know what "usleep(3) is going away in S5R4" means; it wasn't
*in* any S5 releases prior to that, so it's not as if S5R4 got rid of
it.  It's not in the "mainstream" C library, but the manual referred to
in the previous paragraph indicates that it's in the BSD compatibility
code.