Date: Sat, 5 Jun 1999 23:27:23 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Joel Ray Holveck <joelh@gnu.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <199906060627.XAA17722@apollo.backplane.com> References: <54651.928560942@critter.freebsd.dk> <86lndyc6v1.fsf@detlev.UUCP>
next in thread | previous in thread | raw e-mail | index | archive | help
: :> 4. It would be desirable to have per socket timeouts, but would :> require application changes which are unlikely to happen. : :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. : :Cheers, :joelh I see no use whatsoever for being able to specify per-socket keepalive timeouts. -Matt 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?199906060627.XAA17722>