atom feed32 messages in org.freebsd.freebsd-archclose() of active socket does not wor...
FromSent OnAttachments
Kostik BelousovDec 11, 2006 9:11 am 
Arne H. JuulDec 11, 2006 2:40 pm 
David XuDec 11, 2006 4:15 pm 
Arne H. JuulDec 11, 2006 4:50 pm 
David XuDec 11, 2006 5:05 pm 
Daniel EischenDec 11, 2006 5:08 pm 
Bruce EvansDec 11, 2006 9:54 pm 
Poul-Henning KampDec 11, 2006 10:43 pm 
Daniel EischenDec 12, 2006 5:21 am 
Kostik BelousovDec 12, 2006 5:59 am 
Daniel EischenDec 12, 2006 6:24 am 
Daniel EischenDec 12, 2006 6:35 am 
Kostik BelousovDec 12, 2006 6:38 am 
Daniel EischenDec 12, 2006 12:49 pm 
David XuDec 12, 2006 3:29 pm 
Bruce EvansDec 12, 2006 7:28 pm 
Julian ElischerDec 12, 2006 11:12 pm 
Bruce EvansDec 13, 2006 3:28 am 
David XuDec 13, 2006 4:10 am 
Daniel EischenDec 13, 2006 6:23 am 
Robert WatsonDec 20, 2006 8:22 am 
Daniel EischenDec 20, 2006 10:28 am 
David XuDec 20, 2006 4:19 pm 
Julian ElischerDec 21, 2006 5:02 am 
Robert WatsonDec 21, 2006 5:46 am 
Robert WatsonDec 21, 2006 7:21 am 
Daniel EischenDec 21, 2006 9:15 am 
John-Mark GurneyDec 21, 2006 6:17 pm 
David XuDec 21, 2006 6:42 pm 
Daniel EischenDec 21, 2006 7:35 pm 
John-Mark GurneyDec 21, 2006 8:07 pm 
Daniel EischenDec 21, 2006 8:16 pm 
Subject:close() of active socket does not work on FreeBSD 6
From:Daniel Eischen (deis@freebsd.org)
Date:Dec 12, 2006 6:35:23 am
List:org.freebsd.freebsd-arch

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.