🚀 go-pugleaf

In <BHxB8n.I0y@world.std.com> steveo@world.std.com (Steven W Orr) writes:

> In article <1992Jan12.160923.3432@mnemosyne.cs.du.edu> trussell@isis.cs.du.edu (Tim Russell) writes:
> >trevor@trevan.uucp writes:
> >
> >>2) The new PEX code uses itimer which does not seem exist on SCO.
> >
> >    Nope..  Although my understanding is that 3.2v4 will have itimer support
> >in it, which is, I know, small consolation for the here and now.  I'm really
> >not familiar with how involved itimer() is, but if it's just a simple wait,
> >SCO does have a nap() call that you might want to look into.
> >
> >--
> >   Tim Russell               Omaha, NE           trussell@isis.cs.du.edu
> 
> 
> Regarding the nap call from -lx, can someone tell me how it works? Is
> it a busy wait or is there something actually useful there that
> suspends the program?

The nap call is like sleep except that it takes an argument in
milliseconds instead of seconds.  Setitimer is like alarm, except that
it takes a timeval structure (microsecond resolution) instead if
seconds.  Unfortunately for you nap and setitimer have different
semantics so nap cannot take setitimer's place.

What is the length of time that setitimer is being called with?  If it
is in the second range, your best bet would just be to call
alarm(nseconds).

---
Larry Philps,	 SCO Canada, Inc.
Postman:  130 Bloor St. West, 10th floor, Toronto, Ontario.  M5S 1N5
InterNet: larryp@sco.COM  or larryp%scocan@uunet.uu.net
UUCP:	  {uunet,utcsri,sco}!scocan!larryp
Phone:	  (416) 922-1937