Date: Wed, 3 Apr 1996 14:30:58 PST From: Bill Fenner <fenner@parc.xerox.com> To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: phk@critter.tfs.com (Poul-Henning Kamp), hackers@freebsd.org Subject: Re: SO_KEEPALIVE - New feature patch enclosed. Message-ID: <96Apr3.143103pst.177475@crevenia.parc.xerox.com> In-Reply-To: Your message of "Wed, 03 Apr 1996 09:17:03 PST." <199604031717.LAA00364@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96Apr3.143103pst.177475>