From owner-freebsd-questions Mon Mar 25 23:51: 5 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 1FC5437B41A for ; Mon, 25 Mar 2002 23:51:01 -0800 (PST) Received: from mira-sjcm-2.cisco.com (mira-sjcm-2.cisco.com [171.69.24.14]) by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g2Q7p0K25538 for ; Mon, 25 Mar 2002 23:51:00 -0800 (PST) Received: from cbshost-12-155-143-107.sbcox.net (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjcm-2.cisco.com (Mirapoint) with ESMTP id ACF38034; Mon, 25 Mar 2002 23:50:31 -0800 (PST) Date: Mon, 25 Mar 2002 23:50:59 -0800 Mime-Version: 1.0 (Apple Message framework v481) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Question re. tcp keepalives From: Richard Johnson To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <368CE542-408E-11D6-ACE0-0003939711FE@cisco.com> X-Mailer: Apple Mail (2.481) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I noticed that with previous versions of FreeBSD (such as 4.3) I could iconify an xterm window, go on a trip for a week, even taking my computer with me and reconfiguring the ethernet interface, then bring it back, reconfigure the ethernet back to the same address, and finally uniconify the xterm window, and if nothing had done any output the window would still be there! I notice that this capability fails to function in 4.4 (and also in MacOS X, by the way). Looking at kernel variables I found: % sysctl -a | grep keepalive net.inet.tcp.always_keepalive: 1 so I changed it to "0" figuring this would take care of the issue. It didn't. Now I'm working on MacOS X and I noticed the same kernel variable and that it's already "0". Having verified that this is FALSE on both the MacOS X and the FreeBSD system, if I put either system to sleep for more than an hour or so (I'm sure of the exact timing) I notice that the connection dies. Is there some way I get back the capability to leave TCP connections suspended for long periods of time? It was really nice! /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message