Anonymous | Login | 2024-04-26 03:38 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0001160 | [1003.1(2008)/Issue 7] System Interfaces | Editorial | Clarification Requested | 2017-09-03 00:40 | 2019-01-24 16:13 | ||
Reporter | Paul Gilmartin | View Status | public | ||||
Assigned To | ajosey | ||||||
Priority | normal | Resolution | Rejected | ||||
Status | Closed | ||||||
Name | Paul Gilmartin | ||||||
Organization | |||||||
User Reference | |||||||
Section | System Interfaces: read(): Errors | ||||||
Page Number | read() ERRORS | ||||||
Line Number | 5-7 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0001160: Condition for EAGAIN inverted. | ||||||
Description |
I read under read(): ERRORS These functions shall fail if: [EAGAIN] The file is neither a pipe, nor a FIFO, nor a socket, the O_NONBLOCK flag is set for the file descriptor, and the thread would be delayed in the read operation. Doesn't make sense. Documentation for several other UNIX-y systems says such as "is either a pipe, a FIFO, or a socket, ..." |
||||||
Desired Action |
Change "is neither a pipe, nor a FIFO, nor a socket, ..." to "is either a pipe, a FIFO, or a socket, ..." (Should this apply also to a TTY?) Thanks, gil |
||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |