Re: close() of active socket does not work on FreeBSD 6
- From: Daniel Eischen <deischen@xxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 09:19:09 -0500 (EST)
On Mon, 11 Dec 2006, Daniel Eischen wrote:
Common sense leads me to think that a close() should release
threads in IO operations (reads/writes/selects/polls) and
return EBADF or something appropriate. At least when behavior
is not dictated by POSIX or other historical/defactor behavior.
BTW, I tested the behavior on Solaris. Solaris returns EBADF
with the posted sample C program.
--
DE
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- References:
- Re: close() of active socket does not work on FreeBSD 6
- From: Kostik Belousov
- Re: close() of active socket does not work on FreeBSD 6
- From: Arne H. Juul
- Re: close() of active socket does not work on FreeBSD 6
- From: David Xu
- Re: close() of active socket does not work on FreeBSD 6
- From: Arne H. Juul
- Re: close() of active socket does not work on FreeBSD 6
- From: Daniel Eischen
- Re: close() of active socket does not work on FreeBSD 6
- Prev by Date: Re: close() of active socket does not work on FreeBSD 6
- Next by Date: Re: close() of active socket does not work on FreeBSD 6
- Previous by thread: Re: close() of active socket does not work on FreeBSD 6
- Index(es):