|
On Wed, 2004-08-11 at 07:15 -0700, Yunfeng Hou wrote:
> --- Kjetil Torgrim Homme <kjetilho@xxxxxxxxxx> wrote:
> > I was a bit annoyed to find that the proc values (or sysctl) had no
> > effect in the RHEL WS 3.0 kernel, so I guess it's good they are gone so
> > no confusion can happen. you have to use the setsockopt interface
> > instead, this is what ipvsadm --set does.
>
> There are a bunch of timeouts which are not possible
> to set by ipvsadm --set command.
>
> /proc/sys/net/ipv4/vs/timeout_close
> /proc/sys/net/ipv4/vs/timeout_closewait
> /proc/sys/net/ipv4/vs/timeout_established
> /proc/sys/net/ipv4/vs/timeout_finwait
> /proc/sys/net/ipv4/vs/timeout_icmp
> /proc/sys/net/ipv4/vs/timeout_lastack
> /proc/sys/net/ipv4/vs/timeout_listen
> /proc/sys/net/ipv4/vs/timeout_synack
> /proc/sys/net/ipv4/vs/timeout_synrecv
> /proc/sys/net/ipv4/vs/timeout_synsent
> /proc/sys/net/ipv4/vs/timeout_timewait
> /proc/sys/net/ipv4/vs/timeout_udp
sounds like you have an itch to scratch :-)
(``"The One True OSS Motivation" is scratch your own itch.'')
--
Kjetil T.
|
