public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Chin <leechin@mail.com>
To: linux-kernel@vger.kernel.org
Subject: socket close problems
Date: Tue, 20 Mar 2001 21:27:28 -0500 (EST)	[thread overview]
Message-ID: <382436856.985141648588.JavaMail.root@web584-mc> (raw)

Hi,
On linux I have the following problem:
I accept connections from client sockets, read the request and send data
back and close the socket.

After a while, I run out of file descriptors... and when I run netstat, all
my connections to the clients are in state CLOSING...  and I know the client
has received all the data and disconnected too.

What could I be doing wrong?  The socket is set obtained via the accept
system call.  I set the socket to non blocking via fcntl and use
SO_REUSEADDR via setsockopt... and after using the socket for read and
write, I simply call shutdown followed by a close

Thanks
Lee


______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup

                 reply	other threads:[~2001-03-21  2:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=382436856.985141648588.JavaMail.root@web584-mc \
    --to=leechin@mail.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