linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jens Knoell" <jens@surefoot.com>
To: Gustavo Guillermo <gustavo@compunauta.com>, linux-admin@vger.kernel.org
Subject: Re: Hello, I have port busy after server die.
Date: Thu, 12 Feb 2004 13:08:37 -0700	[thread overview]
Message-ID: <013701c3f1a3$fff25260$6f00000a@jenswin2k> (raw)
In-Reply-To: 20040213.3002000.1658383148@linux.local

Gustavo Guillermo wrote:
> Hello everyone, I have a nice question, I ran a WebServer, and after 8
> days hangs and die, but TCP port 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.
>
> There is some C function or command or anything that can release this
> port?

The solution is actually to find out what makes the server die in the first
place. The port gets released as soon as the last instance of the service
gets killed. Since you didn't specify what software you're running I can't
get more specific than that.

Jen


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  3:00 Hello, I have port busy after server die Gustavo Guillermo
2004-02-12 20:08 ` Jens Knoell [this message]

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='013701c3f1a3$fff25260$6f00000a@jenswin2k' \
    --to=jens@surefoot.com \
    --cc=gustavo@compunauta.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).