mts@utai.UUCP (Martin Stanley) (04/02/85)
I am looking for a way to do asynchronous I/O under System V in
a similar way to the BSD select() call.
Any help would be appreciated.
Thanks.
--
Martin Stanley
Department of Computer Science
University of Toronto
Toronto, ON
M5S 1A4
USENET: {cornell,decvax,ihnp4,linus,utzoo,uw-beaver}!utcsri!utai!mts
CSNET: mts@toronto
ARPANET: mts.toronto@csnet-relay
Please use one of the above three addresses, not necessarily the address
in the mail header.mts@utai.UUCP (Martin Stanley) (04/03/85)
In article <408@utai.UUCP> I wrote: >> >> >> I am looking for a way to do asynchronous I/O under System V in >> a similar way to the BSD select() call. >> Any help would be appreciated. >> Thanks. I guess I should have stated that I am intending to to asynchronous I/O on pipes, rather than on ttys. Thanks again. -- Martin Stanley Department of Computer Science University of Toronto Toronto, ON M5S 1A4 USENET: {cornell,decvax,ihnp4,linus,utzoo,uw-beaver}!utcsri!utai!mts CSNET: mts@toronto ARPANET: mts.toronto@csnet-relay Please use one of the above three addresses, not necessarily the address in the mail header.
gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) (04/06/85)
> I am looking for a way to do asynchronous I/O under System V in > a similar way to the BSD select() call. Nope. The closest you can come is to use O_NDELAY reads, the minimum-character-count & -time kludges in termio, and sometimes FIFOs. Select() is supposed to appear at some future date along with stream I/O. This is about the ONLY "foreign" syscall I find useful in applications developed under our UNIX System V emulation on 4.2BSD. Part of the reason it is taking a while to show up in the AT&T product is that it necessitates modifying all the device drivers.