![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| SCO Santa Cruz Operation (SCO) was a software company based in Santa Cruz, California which was best known for selling three UNIX variants for Intel x86. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| need help with sockets | crunchyuser | High Level Programming | 1 | 10-01-2008 01:55 AM |
| HELP!! TLI vs Sockets? | adiaconou | UNIX for Dummies Questions & Answers | 1 | 06-10-2007 09:30 PM |
| Sockets in use | kjbaumann | SUN Solaris | 1 | 07-14-2006 11:06 AM |
| sockets | kirpond | UNIX for Dummies Questions & Answers | 2 | 05-22-2006 09:57 AM |
| sockets... | devy8 | High Level Programming | 1 | 07-02-2001 06:14 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
How can I change timers for TCP/IP sockets in SCO Unix 7.1.1
__________________
Hohoho |
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
Check out the man page for "tcp". Here's a little bit of it:
The TCP_KEEPIDLE option can be used to control the start interval for TCP keep-alive messages. Normally, when enabled via SO_KEEPALIVE, keep-alives do not start until the connection has been idle for 2 hours. This option can be used to alter this interval. The option value should be specified in seconds. The minimum is restricted to 10 seconds. Setting TCP_KEEPIDLE to 0 restores the keep-alive start interval to the default value. Normally TCP will send a keep-alive every 75 seconds once the connection has been idle for the KEEPIDLE period. Keep-alives may be sent more frequently by using the TCP_KEEPINTVL option to specify the interval in seconds. The minimum is restricted to 1 second. Setting TCP_KEEPINTVL to 0 restores the keep-alive interval to the default value. Normally TCP will send 8 keep-alives prior to giving up. This number may be altered by using the TCP_NKEEP option to specify the desired number of keep-alives. The minimum value is constrained to be 1. Setting TCP_NKEEP to 0 restores the keep-alive interval to the default value. Normally TCP will try to retransmit for 511 seconds before dropping a connection. This value can be changed using the TCP_MAXRXT option. Setting TCP_MAXRXT to a value between 180 and 2^32-2 causes TCP to wait that number of seconds before giving up. Setting TCP_MAXRXT to 0 restores the retransmission interval to the default value. Setting the retransmission interval to 2^32-1 (0xffffffff) causes TCP to retransmit forever. The retransmission period cannot be set to less than three minutes (180 seconds). Hope this helps... |
|||
| Google The UNIX and Linux Forums |