[lkml]   [2000]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: poll(2) semantics changed in 2.4.0-? vs. 2.2.16?
On Fri, Oct 06, 2000 at 02:13:45AM +0200, Martin Diehl wrote:
> So, for me the 2.4.0-test9 behavior does not only differ from 2.2 and what
> manpages say - I'm just wondering how to detect the unreachable peer port?
> poll()-timeout means no response at all, which is sth different and forces
> blocking for some time. Nonblocking recvfrom() without poll() wouldn't
> help, since the pending error isn't passed to it either.

Alexey Kuznetsov ( changed it. Ask him why he did it,
I agree with you that it would make more sense to keep the old behaviour
(even though it is differing from most other BSD sockets implementations)

To answer your question: you'll only get the error reported now when the
UDP socket is either connect(2)ed or when you enabled asynchronous
error reporting using IP_RECVERR.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:39    [W:0.085 / U:0.368 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site