termios.3: Add descriptive titles to noncanonical read() cases

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-03-21 15:15:06 +01:00
parent a9f0126fa6
commit f8f8b9c1f6
1 changed files with 4 additions and 4 deletions

View File

@ -725,7 +725,7 @@ determine the circumstances in which a
.BR read (2) .BR read (2)
completes; there are four distinct cases: completes; there are four distinct cases:
.TP .TP
MIN == 0; TIME == 0: MIN == 0, TIME == 0 (polling read)
If data is available, If data is available,
.BR read (2) .BR read (2)
returns immediately, with the lesser of the number of bytes returns immediately, with the lesser of the number of bytes
@ -734,12 +734,12 @@ If no data is available,
.BR read (2) .BR read (2)
returns 0. returns 0.
.TP .TP
MIN > 0; TIME == 0: MIN > 0, TIME == 0 (blocking read)
.BR read (2) .BR read (2)
blocks until MIN bytes are available, blocks until MIN bytes are available,
and returns up to the number of bytes requested. and returns up to the number of bytes requested.
.TP .TP
MIN == 0; TIME > 0: MIN == 0, TIME > 0 (read with timeout)
TIME specifies the limit for a timer in tenths of a second. TIME specifies the limit for a timer in tenths of a second.
The timer is started when The timer is started when
.BR read (2) .BR read (2)
@ -754,7 +754,7 @@ If data is already available at the time of the call to
.BR read (), .BR read (),
the call behaves as though the data was received immediately after the call. the call behaves as though the data was received immediately after the call.
.TP .TP
MIN > 0; TIME > 0: MIN > 0, TIME > 0 (read with interbyte timeout)
TIME specifies the limit for a timer in tenths of a second. TIME specifies the limit for a timer in tenths of a second.
Once an initial byte of input becomes available, Once an initial byte of input becomes available,
the timer is restarted after each further byte is received. the timer is restarted after each further byte is received.