Opened 9 years ago
Closed 6 years ago
#12219 closed bug (invalid)
Sometimes timeouts return B_WOULD_BLOCK not B_TIMED_OUT
| Reported by: | waddlesplash | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | - General | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Not sure why this happens, but I've seen it in Python and now in mail_daemon. This occurs after the operation has clearly timed out (~10-15s).
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Are you talking about sockets at all? Your report is pretty unspecific to be able to do anything about it.
comment:3 by , 9 years ago
Yes, sorry, it is about sockets. I've been able to reproduce it quite easily by making mail_daemon or Python try to fetch an address that resolves but times out when attempting to connect.
comment:4 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
If you're talking about timeouts from sockets with
SO_SNDTIMEOorSO_RCVTIMEOset then that's the correct behaviour.