| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
In the documentation (V4.0) for the t_optmgmt routine, the statement
"Note
Although other transport providers may support the t_optmgmt
function, the Digital UNIX TCP transport provider does not.
See the transport provider documentation for information about
option management.
See t_optmgmt(3) for more information."
is made. The man page for t_optmgmt(3) has no references to
any restrictions on its use.
If t_optmgmt is unsupported, what supported alternatives are there
for this? The goal is to set the equivalent of TCP_KEEPALIVE
(from the xti_internet(7) man page).
A similar question was asked in Note 5618.0 of the ALPHA_OSF_IFT
notes file with response.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9003.1 | t_optmgmt alternatives? | NETRIX::"[email protected]" | Kris Corwin | Tue Mar 04 1997 13:49 | 5 |
Masha didn't have time to post before leaving on a business trip, but here is her response: we do support t_optmgmnt for xpg4 (starting with v4.0, to the capacity specifies by xpg4 x/open manual. [Posted by WWW Notes gateway] | |||||
| 9003.2 | CSC64::BLAYLOCK | If at first you doubt,doubt again. | Wed Mar 05 1997 16:46 | 6 | |
Thanks for the information and I have passed that on to my customer. I will submit the documentation change request to get an update to the Network Programming Guide changed to reflect this. | |||||