From owner-freebsd-hackers  Mon Apr  1 15:00:34 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA10032
          for hackers-outgoing; Mon, 1 Apr 1996 15:00:34 -0800 (PST)
Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA10027
          for <hackers@freebsd.org>; Mon, 1 Apr 1996 15:00:28 -0800 (PST)
Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.6.12) id OAA14661; Mon, 1 Apr 1996 14:57:54 -0800 (PST)
Date: Mon, 1 Apr 1996 14:57:53 -0800 (PST)
From: Jaye Mathisen <mrcpu@cdsnet.net>
To: Joe Greco <jgreco@brasil.moneng.mei.com>
cc: hackers@freebsd.org
Subject: Re: SO_KEEPALIVE
In-Reply-To: <199604011838.MAA24760@brasil.moneng.mei.com>
Message-ID: <Pine.BSF.3.91.960401145749.14257W-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



I would love this.

On Mon, 1 Apr 1996, Joe Greco wrote:

> Question, stupid, nonetheless a question:
> 
> Does anybody see any advantage to allowing for a way to set a systemwide
> SO_KEEPALIVE default of ON?
> 
> My reason for asking:  from time to time, I run into situations where
> software does not correctly terminate connections, most often due to broken
> Portmasters or broken TCP/IP implementations.  For example,
> 
> smp       2983  0.0  0.0   412  348 ??  I    13Mar96    0:01.79 -ws1-6.gmttech.ods.net: smp: STOR test.zip                                  (ftpd)
> 
> or the dozens of hung nnrp processes that get into write() and never get out
> on daily-planet.execpc.com.  My usual fix is to patch the source to enable
> KEEPALIVE...
> 
> I don't mind a local kernel patch but it seems to me that many ISP's might 
> find this useful.
> 
> ... JG
>