There is code in FAHClient to do just that, the problem is that it is not 100% at doing the detection. As an example, I was having network issues a few months ago that were ultimately traced to a combination of a bad DSL filter and bad phone line connection in my house. During that time one or another of my systems would lose the connection or have it slow down a lot. Checking the logs the lost connection was restarted most times, better than 9 out 10, but that restart could be as much as 15, 30 or more minutes later at times. Other times it would be within a few minutes of the last upload or download progress shown in the log.ifolder wrote:Isn't it possible to add in FAHClient a download/upload supervision thread that monitors the network connections and kills and restarts lost connections?
It could be understandable that under bad network conditions connections can be lost but it isn't that this event hangs (partly) FAHClient and requires a reboot of the computer.
It may be OS dependent but when FAHClient hangs for me recovering from a stalled upload or download only takes stopping the existing FAHClient process and restarting a new one. This is on OS X. However that is a bit of a pain in the neck, so I usually just take advantage of the situation and use it for doing any OS updates and rebooting as part of the process.
Finally, in the case of the CS not liking results that is still under investigation. It would be easier if it actually was a 100% drop rate, but it has not been that. So they are looking into why some are dropped when others are not and have not yet found an answer.
Also my internet connection is fine. We have different VPN. And these are really sensitive with errors. None if it reacted in any way last night.