bug: select() for sockets returned by accept() returns always ready for write (sel.always_ready 1)

Hi, I am using non-blocking sockets in a small server software. Select() seems to indicate that sockets returned by accept() are always ready for write. This causes 99% cpu usage since the socket gets always selected as writeable and after that write returns EAGAIN and again we go to the select

Re: bug: select() for sockets returned by accept() returns always ready for write (sel.always_ready 1)

I have now tested with the latest snapshot (2003-Jan-28) and now it seems to work OK. Thanks. - Risto > From: Corinna Vinschen > Date: Tue, 28 Jan 2003 16:33:59 +0100 > > Thanks for the report. It looks pretty much as if you're right here. > I've set the returned file descriptor to connected