|
From: | Simon Goldschmidt |
Subject: | [lwip-devel] [bug #52684] Should read() return ETIMEDOUT on a timeout? |
Date: | Sun, 17 Dec 2017 16:21:44 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 |
Update of bug #52684 (project lwip): Status: None => Invalid Open/Closed: Open => Closed _______________________________________________________ Follow-up Comment #2: > Looking at the Linux man pages it appears that it should > return ETIMEDOUT if blocked Where did you read that? It says we should return ETIMEDOUT on a transmission timeout. This mixes RX with TX, and is not what you seemed to indicate? Anyway, closing as requested :-) _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?52684> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |