From owner-freebsd-hackers Tue Apr 2 09:08:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA09414 for hackers-outgoing; Tue, 2 Apr 1996 09:08:20 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA09408 for ; Tue, 2 Apr 1996 09:08:17 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0u49Xf-0003wkC; Tue, 2 Apr 96 09:06 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id RAA01210; Tue, 2 Apr 1996 17:06:45 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Joe Greco cc: hackers@freebsd.org Subject: Re: SO_KEEPALIVE In-reply-to: Your message of "Tue, 02 Apr 1996 10:10:14 CST." <199604021610.KAA26215@brasil.moneng.mei.com> Date: Tue, 02 Apr 1996 17:06:40 +0000 Message-ID: <1208.828464800@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Question, stupid, nonetheless a question: > > > > > > Does anybody see any advantage to allowing for a way to set a systemwide > > > SO_KEEPALIVE default of ON? > > > > make a sysctl variable for this. It's really easy. > > Yeah, well, that's nice :-) I wanted to know if there would be any general > interest. I'm not a kernel hacker so it would take a bit of expenditure of > effort on my part to figure all that out, yadda yadda yadda, and if it was > something that would not make it into -current, I would opt for a quick and > dirty hack. > > Can anyone suggest an appropriate name for such a variable? sysctl.inet.tcp.keepalive taking a boolean argument. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.