Tue Jun 22 20:17:42 CEST 2004
Per Hedeland wrote:
> David Hopwood <> wrote:
>>TCP_KEEPIDLE et al are not Linux-specific; AFAICS they seem to be supported
>>on all BSD-derived TCP stacks (most Unices including OS X, also OpenVMS, but
> Interesting - do you have some other example of "most Unices"?
> The "BSD-derived" would seem to be misleading, since they're not in the
> latest and greatest FreeBSD (5.2.1), nor can I find them in the online
> tcp(4) man pages of current OpenBSD or NetBSD.
You're right -- I was confused by the fact that many stacks use internal
variables "tcp_keepidle", etc., but these are not socket options. Taking
this into account, I can only find three Unices that support these options:
Tru64 (Digital/HP/Compaq), MP-RAS (NCR), and Linux.
> I also checked the tcp(7P) man
> page of Solaris 8 and 9, not there either, though I did find an
> apparently undocumented TCP_KEEPALIVE, that might possibly be a
> setsockopt combining SO_KEEPALIVE and Linux TCP_KEEPIDLE, in the include
> files of Solaris 8 (nothing corresponding to TCP_KEEPINTVL/TCP_KEEPCNT
TCP_KEEPALIVE is defined by the X/Open Transport Interface. At least MAC OS
(Open Transport), OS/390, SCO UnixWare, and AIX also support it.
See <http://nscp.upenn.edu/aix4.3html/libs/commtrf2/Options.htm> or
David Hopwood <>
More information about the erlang-questions