From: Stelian Pop <stelian.pop@fr.alcove.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: socket write(2) after remote shutdown(2) problem ?
Date: Fri, 5 Apr 2002 12:47:33 +0200 [thread overview]
Message-ID: <20020405104733.GD16595@come.alcove-fr> (raw)
In-Reply-To: <20020405095038.GB16595@come.alcove-fr> <20020405.020443.115246313.davem@redhat.com>
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
next prev parent reply other threads:[~2002-04-05 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:50 socket write(2) after remote shutdown(2) problem ? Stelian Pop
2002-04-05 10:04 ` David S. Miller
2002-04-05 10:47 ` Stelian Pop [this message]
2002-04-05 10:44 ` David S. Miller
2002-04-05 10:55 ` Stelian Pop
2002-04-05 11:02 ` David S. Miller
2002-04-05 12:00 ` Stelian Pop
2002-04-05 12:04 ` David S. Miller
2002-04-05 12:23 ` Stelian Pop
2002-04-05 12:59 ` Stelian Pop
[not found] <20020405104733.GD16595@come.alcove-fr.suse.lists.linux.kernel>
[not found] ` <20020405.024435.88131177.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <20020405105509.GE16595@come.alcove-fr.suse.lists.linux.kernel>
[not found] ` <20020405.030251.28451401.davem@redhat.com.suse.lists.linux.kernel>
2002-04-05 11:47 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020405104733.GD16595@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox