As a fix for a connection timeout problem I was having (stupid Cisco firewall dropping a connection after 1 hour of idle time with no notification on either end) I reduced the tcp keepalive time from the default 2 hours to 45 minutes. When testing this, I simply changed the value in /proc/sys/net/ipv4/tcp_keepalive_time. In order to get this to apply on boot, I added: net.ipv4.tcp_keepalive_time = 2700 to the sysctl.conf file. Last week we had to move the server to a different rack. On bootup the setting was lost (it was back at the default 7200). On all other Linux systems I have (2 RH and a Gentoo), sysctl settings in this file are applied on bootup. SUSE doesn't seem to care about it (which explains why it was empty). Do I have to explicitly make the sysctl call in one of the bootup scripts (and if so, which one), or is there somewhere else I should be looking? -- trey
You have to issue this command chkconfig boot.sysctl on On Thu, 2004-08-19 at 10:16, Trey Gruel wrote:
As a fix for a connection timeout problem I was having (stupid Cisco firewall dropping a connection after 1 hour of idle time with no notification on either end) I reduced the tcp keepalive time from the default 2 hours to 45 minutes. When testing this, I simply changed the value in /proc/sys/net/ipv4/tcp_keepalive_time. In order to get this to apply on boot, I added:
net.ipv4.tcp_keepalive_time = 2700
to the sysctl.conf file.
Last week we had to move the server to a different rack. On bootup the setting was lost (it was back at the default 7200).
On all other Linux systems I have (2 RH and a Gentoo), sysctl settings in this file are applied on bootup. SUSE doesn't seem to care about it (which explains why it was empty). Do I have to explicitly make the sysctl call in one of the bootup scripts (and if so, which one), or is there somewhere else I should be looking?
-- trey -- Thank you,
Matt Duval Sr. Network Engineer HealthTrans www.healthtrans.com "Transforming Healthcare, One Transaction At A Time" (720) 493-8252 6061 South Willow Drive Suite 125 Greenwood Village, CO 80111
I was having the same problems with boot.sysctl also. However I
cannot get chkconfig boot.sysctl on to hold the settings. After I
issue this command I immediately check chkconfig --list and it is
still set to off for all runlevels. Do either of you know why this
might be happening? What could I be missing?
Thanks!
Derek
On Thu, 19 Aug 2004 11:34:36 -0600, Matt T. Duval
You have to issue this command
chkconfig boot.sysctl on
On Thu, 2004-08-19 at 10:16, Trey Gruel wrote:
As a fix for a connection timeout problem I was having (stupid Cisco firewall dropping a connection after 1 hour of idle time with no notification on either end) I reduced the tcp keepalive time from the default 2 hours to 45 minutes. When testing this, I simply changed the value in /proc/sys/net/ipv4/tcp_keepalive_time. In order to get this to apply on boot, I added:
net.ipv4.tcp_keepalive_time = 2700
to the sysctl.conf file.
Last week we had to move the server to a different rack. On bootup the setting was lost (it was back at the default 7200).
On all other Linux systems I have (2 RH and a Gentoo), sysctl settings in this file are applied on bootup. SUSE doesn't seem to care about it (which explains why it was empty). Do I have to explicitly make the sysctl call in one of the bootup scripts (and if so, which one), or is there somewhere else I should be looking?
-- trey -- Thank you,
Matt Duval Sr. Network Engineer HealthTrans www.healthtrans.com "Transforming Healthcare, One Transaction At A Time" (720) 493-8252 6061 South Willow Drive Suite 125 Greenwood Village, CO 80111
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Derek Dave -
Matt T. Duval -
Trey Gruel