View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00011601003.1(2008)/Issue 7System Interfacespublic2017-09-03 00:402019-01-24 16:13
ReporterPaul Gilmartin Assigned Toajosey  
PrioritynormalSeverityEditorialTypeClarification Requested
Status ClosedResolutionRejected 
NamePaul Gilmartin
Organization
User Reference
SectionSystem Interfaces: read(): Errors
Page Numberread() ERRORS
Line Number5-7
Interp Status---
Final Accepted Text
Summary0001160: Condition for EAGAIN inverted.
DescriptionI 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 ActionChange "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
TagsNo tags attached.

Activities

geoffclare

2017-09-11 15:20

manager   bugnote:0003853

The current text is correct. "These functions" includes pread() which fails with ESPIPE not EAGAIN. Further down there is another EAGAIN that is just for read().

Issue History

Date Modified Username Field Change
2017-09-03 00:40 Paul Gilmartin New Issue
2017-09-03 00:40 Paul Gilmartin Status New => Under Review
2017-09-03 00:40 Paul Gilmartin Assigned To => ajosey
2017-09-03 00:40 Paul Gilmartin Name => Paul Gilmartin
2017-09-03 00:40 Paul Gilmartin Section => System Interfaces: read(): Errors
2017-09-03 00:40 Paul Gilmartin Page Number => read() ERRORS
2017-09-03 00:40 Paul Gilmartin Line Number => 5-7
2017-09-11 15:20 geoffclare Note Added: 0003853
2019-01-24 16:13 Don Cragun Interp Status => ---
2019-01-24 16:13 Don Cragun Resolution Open => Rejected
2019-01-24 16:13 Don Cragun Status Under Review => Closed