Re: Turn off a PC:Problems on C/S

not@hoople.demon.co.uk (Mark Bradshaw) wrote: >SO_KEEPALIVE is, as far as I know, a TCP/IP-only option. It is present >because on wide area networks it is difficult to tell if the remote site >has disappeared or is just taking a while to respond. > >If SO_KEEPALIVE is enabled at BOTH ends of the connection then what >happens is when the server has not heard from the client for a specified >period of time if sends a "Are you there?" packet to the client to see >if the client is still there. If no reply, it tries again a few times >and, presuming no response, closes the processes which were using the >socket. > >On the UNIX systems I have looked at this the server waits for 2 hours >before checking on the client. It then sends 5 or 6 "hello" packets >spaced at about 5 minute intervals before shutting down the socket. So >your "left-behind process" on the server Sally will remain for 2 and a >half hours before being closed down (and possibly coredumping - depends > Hi, is the parameter SO_KEEPALIVE a kernel parameter? Where are changes necessary??? Please give me a hint... Dirch +----------------------------------------------------------------------------+ | Dirch Scheer email: scheer@stadt-mh.de | | Amt 10-3 Tel. : +49 208 455 1006 | | Stadtverwaltung (snail-)Mail : Ruhrstr. 32 | | Muelheim an der Ruhr D-45468 Muelheim an der Ruhr | |----------------------------------------------------------------------------| | Inspiration gave them the motivation to move on out their isolation | +----------------------------------------------------------------------------+