lkml.org 
[lkml]   [2002]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: socket write(2) after remote shutdown(2) problem ?
On Fri, Apr 05, 2002 at 02:44:35AM -0800, David S. Miller wrote:

> > 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.
>
> Oh I see now. Here is what should happen:
>
> * server shutdown(ALL)
> * the write() should succeed on the client

So this is really supposed to succeed then... Somewhat illogical to
me...

> * client socket receives a TCP reset

How is the client socket supposed to know it received a TCP reset
(I am talking from the application point of view, not the kernel...) ?

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/

\
 
 \ /
  Last update: 2005-03-22 13:25    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site