From owner-freebsd-hackers Wed Apr 3 14:33:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28564 for hackers-outgoing; Wed, 3 Apr 1996 14:33:32 -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 OAA28558 for ; Wed, 3 Apr 1996 14:33:27 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15463(7)>; Wed, 3 Apr 1996 14:31:11 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177475>; Wed, 3 Apr 1996 14:31:03 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Joe Greco cc: phk@critter.tfs.com (Poul-Henning Kamp), hackers@freebsd.org Subject: Re: SO_KEEPALIVE - New feature patch enclosed. In-reply-to: Your message of "Wed, 03 Apr 1996 09:17:03 PST." <199604031717.LAA00364@brasil.moneng.mei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 3 Apr 1996 14:30:58 PST From: Bill Fenner Message-Id: <96Apr3.143103pst.177475@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While we're on this topic, someone asked in comp.protocols.tcp-ip about tuning the keepalive timer, and someone from TGV replied: >Assuming that you're running MultiNet + VMS, then you can - >on a per-socket basis via the TCP_KEEPALIVE socket option (see >ftp://ftp.tgv.com/customer_support/tech-tips/multinet_vms/mnv30021.tip ), >on a systemwide default basis via the TCP_KEEPIDLE and TCP_KEEPINTVL >kernel paramaters (see >ftp://ftp.tgv.com/customer_support/tech-tips/multinet_vms/mnv30092.tip ), >or on a per TCP server basis via the KEEPALIVE-TIMERS parameter in >SERVER-CONFIG. We already have net.inet.tcp.{keepidle,keepintvl} but it might be worth thinking about adding the TCP_KEEPALIVE socket option. Bill P.S. Is it documented anywhere that net.inet.tcp.{keepidle,keepintvl} are in units of 500ms? Should it be?