Re: [cobalt-users] Re: Stuck Connections

["Gerald Waugh" <gerald@xxxxxxxxx>]

gsh wrote
> Ok, as an aside here, having connections repeatedly get stuck in FIN_WAIT
> is often a sign of a poorly configured firewall on the clients end,
> happens when they go nuts and block all kinds of ICMP traffic and
> inadvertantly make it impossible for the client machine to finish telling
> the server that it is closing the connection. The server than ends up
> waiting around for quite a while before it decides it's not gonna get any
> data, not gonna get an error, not gonna get a reset, and finally decides
> to assume a closed socket....it can take half a day for it to give up
> 
Interesting!

Which icmp traffic should one block?
Do you have some ipchains rules to use?

I just looked at proftpd.conf
and they do not use several parameters
TimeoutLogin seconds   #Default is 300
TimeoutIdle seconds       #Default if 600
TimeoutNoTransfer seconds #Default 300
TimeoutStalled seconds  #Default is 3600

Now wouldn't you think that these would kill the process.
Unless some of these may be set to 0, which is for ever.
Is there a way to query these parameters?
Or should one set them implicitly?
Gerald