Date: Sun, 06 Jun 1999 09:20:35 +0200 From: sthaug@nethelp.no To: dillon@apollo.backplane.com Cc: joelh@gnu.org, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <34759.928653635@verdi.nethelp.no> In-Reply-To: Your message of "Sat, 5 Jun 1999 23:27:23 -0700 (PDT)" References: <199906060627.XAA17722@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> :Huh? I was just considering writing the patch for this. What > :application problems would this create? > : > :The worst thing I can see is that it would mean that changing the > :timeout value on a running system wouldn't affect already opened > :sockets. Even that may be changable by an external utility if I can > :think of a way to handle the locking in userland. > : > > I see no use whatsoever for being able to specify per-socket keepalive > timeouts. Well, if it was implemented with the TCP_KEEPALIVE option, it would be one more part of the system that complied with the X/Open specifications. 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?34759.928653635>