Ask a Question related to UNIX Programming, Design and Development.
-
Ketil Johnsen #1
Nonblocking I/O and draining
Hi,
I'm currently writing a prosess that handles a "large" number of serial
ports (listening for data, and sending data on request). I therefore use
nonblocking I/O (open() with O_NONBLOCK) and poll().
I need to know when the data I have written is actually/physically written!
poll() just tells me when the serial device is ready for another write
operation.
tcdrain() will block untill the data is actually/physically written. That is
unacceptable, since this will halt my program for several minutes, when
using low baud-rates.
Is there a way to allow only one write operation at a time?
Is there a way to reduce the buffering?
Any other sollutions are welcome!
(The platform is Solaris)
--
Ketil
Ketil Johnsen Guest
-
Nonblocking Filehandles under Windows
Hi, I am running ActiveState ActivePerl 5.8 under Windows NT and I'd like to use a non-blocking file handle to do socket I/O. I tried the...



Reply With Quote

