New test version to try
here. I forgot to add the 10 second timeout in a few spots in the first one I posted. I think this may result in some error messages in the debug log but hopefully prevent freezing up, we'll see.
Andy, This is what I done:
Downloaded latest update on my primary and secondary computers.
6:05 - launched the secondary TTD (runs on a computer at home). watched it check the redundant.cfg
6:07 - launched the primary TTD (on a computer at work). Watched it check the redundant.cfg
6:09 - Watched the primary check the redundant.cfg successfully.
6:10 - unplugged the Ethernet on my primary machine.
6:11 - when it tried to check the redundant.cfg I got the errors similar to before.
6:12 - plugged back in the Ethernet.
6:17 - Secondary TTD sent out email that Primary was down. <-- I love this idea!!
6:46 - got nothing on the debug screen since 6:11 so I broke the squelch to insure I wasn't locked up and it wasn't.
6:46 - Secondary TTD still working fine.
7:09 - broke squelch on primary and found it locked up. When I put mouse over the TTD screen it said (Not Responding). The log doesn't show anything at the time of lockup.
7:18 - Secondary TTD still working fine.
8:49 - Tone detected by Secondary (I closed the program on the Primary) after delay email was sent.
9:00 - Secondary TTD still working fine.
Obviously the "not responding" is a problem but I would have hoped it would have retried to connect to my FTP server 5 - 10 minutes after the failed attempt but it didn't. It appears to have locked up almost exactly on hour after the failed attempt to reach my FTP server.
Hope this help the debug process!!