Re: [cobalt-users] (no subject)

["Gerald Waugh" <gerald@xxxxxxxxx>]

> 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)
>

Ok, restarting inetd will not work!

But, if you can find the stuck proceses with "netstat -tupan"
tcp        0      0 216.175.178.43:21       216.175.178.40:63385   WAIT
15465/proftpd: admi
Shows that processes 15465 is stuck in wait.
now issue "kill 15465

Gerald