search for: tcp_timeout

...it. /proc and shared memory tools weren't particular useful. Just for context, we are having an intermittent locking index cache locking issue that appears to impact only a subset of our users. The index files are on NFS. It may be fixed by a dovecot patch (we are at 1.1.3), adjusting our tcp_timeout on the servers, upgrading out circa 2000 load balancer, the type and configuration of the multiple simultaneous persistent clients that user is using, etc. lslk, alert logs, strace, testing the most recent 1.1.X version, and file mtime is giving us some information but we want to make everythin...

hi all, have anyone tried changing the tcp setting in the source files ? for eg decreasing the TCP_KEEPALIVE_TIME from 2 hours to say 10 min --> (120*60*HZ) to (10*60*HZ) in include/net/tcp.h ?? changing the parameters in static unsigned long tcp_timeouts[] in net/ipv4/netfilter/ip_conntrack_proto_tcp.c from 5 DAYS to 4 HOURS or from 30 MIN to 10 MIN or both ??? will that change tcp keep alive or packets in conntrack in any way ??.. sorry for being too basic but am trying to think how it can help better my iptables/iproute firewal/bandwidth on...

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 ------- Additional Comments From pmccurdy@net-itech.com 2004-08-04 06:06 ------- We have managed to replicate this bug in-house. It seems to happen to us when we have a machine acting as a NAT router that we saturate with outgoing UDP packets; we use hping2 to generate them from a workstation connected via 100 Mbit

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=49 ------- Additional Comments From laforge@netfilter.org 2003-02-14 08:39 ------- what patches from patch-o-matic do you use? Do you know how to reproduce this behaviour? ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.