> :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, sth...@nethelp.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
