By default, most OS's will keep the sockets open. When you created a socket, you can include the SO_KEEPALIVE option. This will keep the socket open for tcp_keepalive_interval value of the OS, the defult is 2 hours on microsoft and Solaris sysems. If you do not use this socket options they will stay open forever theoretically unless the OS does some type of housekeeping that closes old/stale file descriptors or something similiar since a socket is simply a file descriptor. This keepalive in the OS is configurable through ndd command in solaris or through the registry in Windows.
Thanks everyone for the info. ""sam sneed"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Lets say we have host A 22.12.12.12 and host B 99.99.99.99. Host B is a > server listening on port 3055. Host A connects to the server B and sends > data. Now neither host A or B send anything to each other for 1 hour. Is > the connection still there? Is there a timeout for the connection? I do not > see anything in the RFC's about keepalives for TCP connections, so how would > Host B know the difference between host A not sneding data for a long time > or host A crashes? > If I unplug the power on host A while the TCP connection is up and leave it > unplugged for a week and will the server still have the the connection in > its tables when I do a netstat -an? I doubt it, so I figure the server must > have its own timeout on idle connections? > > Anyone known any real values for these timeouts for various OS's? > > Thanks. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=49032&t=48934 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
