lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 29 Oct 2007 17:59:23 +0900
From:	Simon Horman <>
To:	David Miller <>
Subject: Re: IPVS: use proper timeout instead of fixed value

On Mon, Oct 29, 2007 at 01:35:15AM -0700, David Miller wrote:
> From: Simon Horman <>
> Date: Mon, 29 Oct 2007 16:05:55 +0900 (JST)
> > From: Andy Gospodarek <>
> > 
> > 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.
> > 
> > Signed-off-by: Andy Gospodarek <>
> > Acked-by: Simon Horman <>
> I would apply this but it does not apply to current 2.6.x,
> please resubmit.

I tried against net-2.6 and it seemed to work.
Was I mistaken or should I be using a different tree?


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists