From owner-freebsd-hackers  Wed Apr  3 18:57:07 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA16239
          for hackers-outgoing; Wed, 3 Apr 1996 18:57:07 -0800 (PST)
Received: from multivac.orthanc.com (root@multivac.orthanc.com [206.12.238.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA16227
          for <hackers@freebsd.org>; Wed, 3 Apr 1996 18:57:00 -0800 (PST)
Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7.3/8.7.3) with SMTP id SAA12421; Wed, 3 Apr 1996 18:56:27 -0800 (PST)
Message-Id: <199604040256.SAA12421@multivac.orthanc.com>
From: Lyndon Nerenberg VE7TCP <lyndon@orthanc.com>
To: Bill Fenner <fenner@parc.xerox.com>
cc: hackers@freebsd.org
Subject: Re: SO_KEEPALIVE - New feature patch enclosed. 
In-reply-to: Your message of "Wed, 03 Apr 1996 15:10:56 PST."
             <96Apr3.151106pst.177475@crevenia.parc.xerox.com> 
Date: Wed, 03 Apr 1996 18:56:26 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> These timers are settable system-wide
> using the net.inet.tcp.{keepidle,keepintvl} sysctl options.  I was suggesting
> causing them to be tunable on a per-socket basis like TGV Multinet.  This
> might be useful for servers with different keepalive requirements.

Yes! I'm getting fed up with Netscape leaving hanging ftpd data
connections due to (improperly) aborted LIST commands. I recently hacked the
ftpd code to force KEEP_ALIVE on the data sockets. Being able to tune
the timers on these connections would help even more.

--lyndon