|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001525 |
[1003.1(2016/18)/Issue7+TC2] System Interfaces |
Editorial |
Clarification Requested |
2021-10-15 16:07 |
2022-02-04 10:08 |
|
|
Reporter |
ben_pfaff |
View Status |
public |
|
|
Assigned To |
ajosey |
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Applied |
|
|
|
|
|
Name |
Ben Pfaff |
|
Organization |
|
|
User Reference |
|
|
Section |
close() |
|
Page Number |
689 |
|
Line Number |
23562 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0001525: only the close() of the last fd for a socket should destroy the socket |
|
Description |
The description of close() repeatedly says that various actions only take place when the last fd for an object is closed. For example:
"When all file descriptors associated with a pipe or FIFO special file are closed..."
"When all file descriptors associated with an open file description have been closed, ..."
"The last close() for a STREAM..."
"If fildes refers to the master side of a pseudo-terminal, and this is the last close, ..."
But it does not say that for sockets: "If fildes refers to a socket, close() shall cause the socket to be destroyed." This suggests behavior that implementations do not (and should not) implement. |
|
Desired Action |
Change: "If fildes refers to a socket, close() shall cause the socket to be destroyed."
to: "When all file descriptors associated with a socket have been closed, the socket shall be destroyed." |
| Tags |
tc3-2008 |
|
|
Attached Files |
|
|
|
Relationships 
