Actions
Bug #15482
open
PORT_GET(3C) could be clearer about port_getn and EINTR
Status:
New
Priority:
Low
Assignee:
-
Category:
manpage - manual pages
Start date:
Due date:
% Done:
0%
Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:
External Bug:
Description
From https://log.omnios.org/illumos/2023-03-15#1678901354-571013
"I wonder what would happen to a thread waiting indefinitely for two events where one had already been generated..."
Someone looking at the manpage can see for certain that port_getn can return fewer than the original nget events on ETIME.
One could infer (hopefully correctly) that EINTR will not update nget and will not return any events, but it could probably be a bit more explicit.
Updated by Nahum Shalman 3 months ago
There's also a typo that should get cleaned up when this gets addressed:
The port_getn() function block until the desired number of events
should probably be
The port_getn() function blocks until the desired number of events
Actions