Xref: utzoo comp.unix.questions:31157 comp.unix.wizards:25496
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!bu.edu!cvbnet!mkaminsk
From: mkaminsk@cvbnet.prime.com (mailhost)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: talk session
Message-ID: <1489@cvbnetPrime.COM>
Date: 9 May 91 16:11:20 GMT
References: <azK/EJXR7ndok@idunno.Princeton.EDU>
Sender: postnews@cvbnetPrime.COM
Lines: 31

From article <azK/EJXR7ndok@idunno.Princeton.EDU>, by subbarao@phoenix.Princeton.EDU (Kartik Subbarao):
> In article <1991May7.102219.25557@ssd.kodak.com> weimer@ssd.kodak.com writes:
>>
>>In article <1991May7.084631.10183@prl.dec.com>, boyd@prl.dec.com (Boyd
>>Roberts) writes:
>>|> In article <1991May7.000521.28186@athena.cs.uga.edu>,
>>greg@athena.cs.uga.edu (Greg Whitlock) writes:
>>|> > 		for (i = 0; i < delay; i++)
>>|> > 			;
> You should man usleep(3).

Actually usleep(3) is going away in System V Release 4 (SVr4)
so you can use select(2):

    #include <stdio.h>
    #include <sys/types.h>
    #include <sys/time.h>

    struct timeval      timeout;

    timeout.tv_sec = 0;
    timeout.tv_usec = number_of_microseconds;

    /* call select for it's timeout feature */
    select(1, NULL, NULL, NULL, &timeout);

Of course you may sleep a lot longer than you want -
do to whatever else is happening on the system.

Mark B. Kaminsky   mkaminsk@cvbnet.prime.com
Computervision/Prime Computer, Bedford, Massachusetts, USA