Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!gistdev!flint
From: flint@gistdev.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Timed input
Message-ID: <8800008@gistdev>
Date: 9 Jan 89 23:20:00 GMT
References: <11@rsoft.UUCP>
Lines: 17
Nf-ID: #R:rsoft.UUCP:11:gistdev:8800008:000:949
Nf-From: gistdev.UUCP!flint    Jan  9 17:20:00 1989


Give me multiple alarms at once and I'll think about that: that approach
won't work for me quite often because the alarm is in use for something
else.  (Ex: the alarm is in use to check-point my shared memory to disk
every so often.)  A second problem with alarm is that with timing
granularity of only 1 second it doesn't give me very good accuracy or
control, and I'm stuck with a minimum delay of 1 second.  (I've had
numerous cases where I wanted the time limit to be .1 to .4 seconds and was
forced to choose between 0 and 1.  I've also had customers beat me over
the head because they didn't think that 0.1 seconds granularity was
good enough for them.)  (Of course, they wanted UNIX, they just want
real-time response besides.) 

Flint Pellett, Global Information Systems Technology, Inc.
1800 Woodfield Drive, Savoy, IL  61874     (217) 352-1165
INTERNET: flint%gistdev@uxc.cso.uiuc.edu
UUCP:     {uunet,pur-ee,convex}!uiucuxc!gistdev!flint