linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Taylor <scott@dctchambers.com>
To: linux-admin@vger.kernel.org
Subject: Re: port busy after server die.
Date: Thu, 12 Feb 2004 12:27:13 -0800	[thread overview]
Message-ID: <5.2.1.1.0.20040212122131.00ae33c0@mustang> (raw)
In-Reply-To: <20040213.3084700.512249801@linux.local>

At 07:08 PM 02/12/2004, Gustavo Guillermo wrote:
>Hello everyone, I have a nice question, I ran a WebServer,

What WebServer?

>and after 8
>days hangs and die, but TCP port wasn't released.

How do you know it wasn't released?

>I know that the solution is restart the system, but I see it in other
>times and this server can't be restarted.

Oh, an NT server maybe?  Rebooting Windows is the way, but not if you are 
talking about some flavour of UNIX.  This is a Linux admin list BTW.

>There is some C function or command or anything that can release this
>port?

Stop the server that is keeping the port open.  What port is it?  What is 
running on it?



  reply	other threads:[~2004-02-12 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  3:08 port busy after server die Gustavo Guillermo
2004-02-12 20:27 ` Scott Taylor [this message]
2004-02-12 22:25 ` Glynn Clements
2004-02-14  2:35   ` Gustavo Guillermo

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=5.2.1.1.0.20040212122131.00ae33c0@mustang \
    --to=scott@dctchambers.com \
    --cc=linux-admin@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).