> I suspect what is commonly the problem here is related to the fact > that cvs has such a phase at the beginning where it is scanning > through the file system, which can take quite a while. Some NAT > devices along the path sometimes have timeouts on existing connections > that if no traffic is happening for a while, they are dropped, even > though there hasn't been any FINs on the connection. > So a connection that just don't have any traffic for a while are hit > by this, which is exactly the pattern you have with cvs.
This is the reason some of my ~/.ssh/config files has host * ServerAliveInterval 240 in them. :) Regards, - Håvard
