Problem: when a network connection a,b.c.16:xxxx -> a.b.c.20:yyyy fails, it is to be re-established as soon as possible, but the addresses 0.0.0.0:xxxx (listening for 1+ connect() calls) and a.b.c.d:xxxx (after accept()ing a connect()ion) are in use in the CLOSE_WAIT or FIN_WAIT2 state, or (0.0.0.0) just busy listening, and stay that way for hours, forcing a reboot of the OS to clear the addresses. I could tolerate having to wait a few seconds. There may be a switch or option I'm unaware of such that close(fd) has the desired effect of close_right_now_dammit_this_is_important(fd). Protocol is TCP/IP. Context: systems form a ring passing a token indicating what systems are 'alive' in the ring, also in a star for direct transmission. Systems can die and re-enter asynchronously (sorta like people, eh?) Each system must maintain connections responsively to loss/acquisition among the systems. Brian Brunner brian.t.brunner@xxxxxxxxxxxxxxx (610)796-5838 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.hubbell.com - Hubbell Incorporated ********************************************************************** -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
