From owner-freebsd-hackers  Wed Apr  3 15:11:57 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA01579
          for hackers-outgoing; Wed, 3 Apr 1996 15:11:57 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA01572
          for <hackers@freebsd.org>; Wed, 3 Apr 1996 15:11:54 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15025(13)>; Wed, 3 Apr 1996 15:11:15 PST
Received: by crevenia.parc.xerox.com id <177475>; Wed, 3 Apr 1996 15:11:06 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: fenner@parc.xerox.com, jgreco@brasil.moneng.mei.com
Subject: Re: SO_KEEPALIVE - New feature patch enclosed.
Cc: hackers@freebsd.org
Message-Id: <96Apr3.151106pst.177475@crevenia.parc.xerox.com>
Date: Wed, 3 Apr 1996 15:10:56 PST
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Sorry, I should have been more clear.

I was talking about the "keepidle" and "keepinvtl" timers, which determine
the intervals between keepalives.  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.

>I have no idea where to document it.

Probably in tcp(4).

  Bill