To destruct TCP connections gracefully base on fatal signals does not seem to be a good idea.
I would suggest to put this in the hands of the peer. Between two nodes that have TCP connections, and want to maintain it all the time, it is better to have heart beat sending back and forth, or at least one way (depends on your application). When the heartbeats is gone (not received for a while, or couple retries), the connection should be deemed as gone, then both sides should try to reestablish the connection.
Generally speaking heartbeats should be handled on its own thread, so it is not blocked by anyone else.
The other thing is that, you should look into your code, see whether there is any blocking call in your socket program. If you can, try to avoid them, so you always have the chance to check the connection.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.