Date: Tue, 01 Jun 1999 23:47:42 +0200 From: sthaug@nethelp.no To: mph@astro.caltech.edu Cc: julian@whistle.com, davids@webmaster.com, phk@critter.freebsd.dk, kip@lyris.com, nate@mt.sri.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <29074.928273662@verdi.nethelp.no> In-Reply-To: Your message of "Tue, 1 Jun 1999 13:42:32 -0700" References: <19990601134232.A22685@wopr.caltech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > maybe we should fix our SERVER apps.. > > e.g. telnetd, sshd, etc. to have 1 week timeouts > > IIRC, it is not possible to specify how long the keepalive interval > should be, using the socket interface. Do you suggest we add a new > interface not present in other Unix implementations, or that we make > SO_KEEPALIVE always have a one-week timeout, surprising the other > applications that expect it to be faster? There *is* a well defined interface for this, namely the TCP_KEEPALIVE socket option. This is a *per connection* keepalive timer, and is implemented by for instance Solaris 2.6. See http://www.unix-systems.org/single_unix_specification_v2/xns/xti.h.html Also mentioned in Stevens vol. 2 as far as I can remember. If the FreeBSD kernel implemented TCP_KEEPALIVE, it would be rather simple to set this on an application basis. (No, unfortunately, I'm not offering to implement it.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29074.928273662>