Re: odd behavior on select() after shutdown()

2010-05-18 Thread Kostik Belousov
On Tue, May 18, 2010 at 12:58:05PM +0900, Yoshihiko Sarumaru wrote: > Hi, > > 2010/5/18 Kostik Belousov : > > On Tue, May 18, 2010 at 01:08:50AM +0900, Yoshihiko Sarumaru wrote: > >> Hi all, > >> > >> Select(2) has three arguments to get socket status for read, write and > >> except. > >> After u

Re: odd behavior on select() after shutdown()

2010-05-17 Thread Yoshihiko Sarumaru
Hi, 2010/5/18 Kostik Belousov : > On Tue, May 18, 2010 at 01:08:50AM +0900, Yoshihiko Sarumaru wrote: >> Hi all, >> >> Select(2) has three arguments to get socket status for read, write and >> except. >> After upgrading to 8.0-RELEASE, select() after shutdown(SHUT_WR) returns with >> the status e

Re: odd behavior on select() after shutdown()

2010-05-17 Thread Kostik Belousov
On Tue, May 18, 2010 at 01:08:50AM +0900, Yoshihiko Sarumaru wrote: > Hi all, > > Select(2) has three arguments to get socket status for read, write and except. > After upgrading to 8.0-RELEASE, select() after shutdown(SHUT_WR) returns with > the status exceptfds is set. It means out-of-bound data

odd behavior on select() after shutdown()

2010-05-17 Thread Yoshihiko Sarumaru
Hi all, Select(2) has three arguments to get socket status for read, write and except. After upgrading to 8.0-RELEASE, select() after shutdown(SHUT_WR) returns with the status exceptfds is set. It means out-of-bound data can be read from the socket, but recv() with OOB flag returns ECONNRESET, and