public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Phy Prabab <phyprabab@yahoo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: odd socket behavior
Date: Wed, 31 Aug 2005 08:45:23 -0400	[thread overview]
Message-ID: <4315A663.3070903@tmr.com> (raw)
In-Reply-To: <20050830065344.86508.qmail@web51807.mail.yahoo.com>

Phy Prabab wrote:
> Hello all,
> 
> I am seeing something odd w/sockets.  I have an app
> that opens and closes network sockets.  When the app
> terminates it releases all fd (sockets) and exists,
> yet running netstat after the app terminates still
> shows the sockets as open!  Am I doing something wrong
> or is this something that is normal?

What do you see with lsof? Is there a process associated?

I'm seeing something related with 2.6.13...

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2005-08-31 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  6:53 odd socket behavior Phy Prabab
2005-08-30  7:01 ` Chase Venters
2005-08-31 12:45 ` Bill Davidsen [this message]
2005-09-02 17:52 ` Alex Riesen

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=4315A663.3070903@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phyprabab@yahoo.com \
    /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