[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] (no subject)
- Subject: Re: [cobalt-users] (no subject)
- From: flash22@xxxxxxx
- Date: Wed Oct 3 08:16:07 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Wed, 3 Oct 2001, Scott w wrote:
> > > There are a couple of connections that are stuck for a customer. Is
> >there
> >a
> > > way to kill/reset the connections?
> > >
> >What port are they connected to:
> >restart that service?
> >Gerald
>
> They are connected to FTP. Wouldn't I need to restart inet to restart FTP?
> What is the command to restart inet? I know it is probably one that I will
> kick myself on, but I can't seem to find it...
That won't do anything anyhow, inetd will only reread it's config file....
Given there is a 300 second ftp timeout, they should get 'unstuck' after a
few minutes, in what way are they 'stuck'? You know that netstat will
often show old closed connections for a while of they didn't close cleanly
, right? this is meaningless.....
Only lines ending with 'ESTABLISHED' are in fact really connected, lines
ending with FIN_WAIT, CLOSED are already more or less gone,
they will vanish eventually, the kernel keeps the info around for a
while...(In case a stray lost packet shows up after the fact)
gsh