Xref: utzoo comp.unix.microport:3060 comp.unix.xenix:5497 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!milano!bigtex!pmafire!dave From: dave@pmafire.UUCP (Dave Remien) Newsgroups: comp.unix.microport,comp.unix.xenix Subject: nap in Sys V Keywords: XENIX SysV nap Message-ID: <608@pmafire.UUCP> Date: 30 Mar 89 06:03:30 GMT References: <661@micropen> <743@omen.UUCP> <663@micropen> <1989Mar29.185842.14146@ateng.ateng.com> Reply-To: dave@pmafire.UUCP (Dave Remien) Organization: WINCO, INEL, Idaho Lines: 22 In article <1989Mar29.185842.14146@ateng.ateng.com> chip@ateng.ateng.com (Chip Salzenberg) writes: :>>AT&T sucks for not having a sub-second clock interval. Although XENIX nap() :>>is anemnic compared to BSD ftime(). :> :>Which, of course, means that SysV missed the boat. Except for SysV R3.2, :>which of course includes nap(). There are ways to get sub second sleeps in Sys V 3.[0|1], using a serial port. I've had no problem getting 1/10 second sleeps on any of Bell, Microport, or AT&T. If you're running an older version (pre 3.2), and want the code, drop me a line; it's only a few dozen lines long. I didn't notice that nap() was in the 3.2 lib; I'll have to look. Is that nap() as in curses napms()? If so, even tho' you specify time in milliseconds, Sys V rounds to normal sleep() intervals (in fact, that's what most curse's napms() actually calls). :>-- :>Chip Salzenberg or :>A T Engineering Me? Speak for my company? Surely you jest! :> "It's no good. They're tapping the lines." Dave Remien - WINCO Computer Eng. Group -uunet!pmafire!dave- "Let's just look at the extras on your new car - wire wheel spoke fenders, two way sneeze through wind vents, stars and mudguards, chrome fender dents, and factory air conditioned air, from our fully factory equipped airconditioned factory."