Re: socket write(2) after remote shutdown(2) problem ?

Stelian Pop (stelian.pop@fr.alcove.com)
Fri, 5 Apr 2002 12:47:33 +0200


On Fri, Apr 05, 2002 at 02:04:43AM -0800, David S. Miller wrote:

> From: Stelian Pop <stelian.pop@fr.alcove.com>
> Date: Fri, 5 Apr 2002 11:50:39 +0200
>
> * the client side socket passes in CLOSE-WAIT state
> * the client issues a write on the socket which succeds.
> ...
> Attached are sample codes for the "server" and the "client". Test
> was done on latest 2.4 and 2.5 kernels.
>
> Your client does not do any write()'s after the shutdown call.
> It simply exit(0)'s.

You mean the 'server' ? Even if I add a sleep(600) between the
shutdown() call and the exit() call I get the same behaviour.

Stelian.

-- 
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/