On Thu, May 04, 2006 at 10:51:11PM -0400, Andy Gospodarek wrote: > On Fri, May 05, 2006 at 09:47:56AM +0900, Horms wrote: > > On Thu, May 04, 2006 at 04:11:16PM -0400, Andy Gospodarek wrote: > > > > > > Instead of using the default timeout of 3 minutes, this uses the timeout > > > specific to the protocol used for the connection. The 3 minute timeout > > > seems somewhat arbitrary (though I know it is used other places in the > > > ipvs code) and when failing over it would be much nicer to use one of > > > the configured timeout values. > > > > Hi Andy, > > > > I agree that the current value is somewhat arbitary, > > however I'm more in favour of setting it idependantly > > of other timeouts, perhaps via proc. In any case, > > won't pp->timeout_table[cp->state] be rather long in > > the ESTABLISHED case? > > > > Horms, > > I agree that there could be a long timeout for ESTABLISHED connections, > but I've run across a situation where I need exactly that. When testing > failover from master to backup I realize that all of my interactive > sessions get dropped much sooner than the timeout I've configured (mine > is currently set for much longer than 3 minutes). If I wanted > established connections to timeout quickly I would set the timeout to be > a small value.
Sorry, I missunderstood your patch completely the first time around. Yes I think this is an excellent idea. Assuming its tested and works I'm happy to sign off on it and prod DaveM. -- Horms http://www.vergenet.net/~horms/ - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
