From owner-freebsd-current Tue Jun 1 13:25:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D1BFC14E9D for ; Tue, 1 Jun 1999 13:25:22 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 Jun 99 21:20:46 +0100 (BST) Date: Tue, 1 Jun 1999 21:20:45 +0100 From: David Malone To: Nate Williams Cc: Poul-Henning Kamp , Matthew Hunt , kip@lyris.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601212045.A13137@bell.maths.tcd.ie> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> <199906012015.OAA15519@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199906012015.OAA15519@mt.sri.com>; from Nate Williams on Tue, Jun 01, 1999 at 02:15:05PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 02:15:05PM -0600, Nate Williams wrote: > > Can people live with a one week TCP keepalive as default ? > > Compromise. I like it. One week is certainly adequate for me. If I > leave a link 'active' for longer than that w/out activity, I deserve to > lose the link Surely that violates POLA? That upsets people who have keepalive turned on already and find 1 week is way too long. For instance, we use keepalive to get rid of stuck netscapes, and we'd probably run out of swap or mbufs if it went up to a week. We just managed by putting this in rc.local: sysctl -w net.inet.tcp.always_keepalive=1 Make it a rc.conf knob if anything. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message