linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ratheesh kannoth <ratheesh.ksz@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: close() on tcp socket.
Date: Wed, 6 Apr 2011 16:30:43 +0530	[thread overview]
Message-ID: <BANLkTimLJ4k1KzmzHkz10JvL9HTyb0y+WQ@mail.gmail.com> (raw)

connect() system call establishes a connection as shown in below steps.

1.   |client |  ----------------- syn --------------->  | server |

2.  |Server|  --------------syn+ ack --------------> | client |

3.  | Client | -----------------ack --------------------> | Server |


But establishing connection , client calls close() system call. Client
is sending FIN+ ACK to server  [ i expected only FIN to be sent from
client to server ]

Is this a valid scenario.?  what could be the problem ?


-Ratheesh

             reply	other threads:[~2011-04-06 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 11:00 ratheesh kannoth [this message]
2011-04-06 11:54 ` close() on tcp socket Javier Martinez Canillas
2011-04-06 19:20 ` Glynn Clements
2011-04-17 12:26 ` Mahavir Jain

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=BANLkTimLJ4k1KzmzHkz10JvL9HTyb0y+WQ@mail.gmail.com \
    --to=ratheesh.ksz@gmail.com \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).