Problem with distributed network
Posted: Thu Jul 26, 2012 5:07 pmHi Bitweasil!
I'm here to report an issue with the server mode. As it seems, if for some reason a client goes down (i.e. connection problems), the server keeps announcing that the client is still there, although we can see there is no speed variations, which happens with connected clients. I'm not sure if this is the only case where this happens, I need some further testing. As I'm thinking, it should be possible to implement a solution where the server checks client connectivity from time to time, and if the client doesn't answer within a period of time, it would be removed from the list and it's current WU would be redirected to some other host (or marked as "undone"). Can this be done?
As a side request, is there a way to compile the source on 32-bit Linux systems? Do you know of some guides that could help me do this? Since I'm thinking on using a 32-bit system to run in serveronly mode, limitations with rainbow tables shouldn't be a problem.
Thanks in advance!
Cheers!
I'm here to report an issue with the server mode. As it seems, if for some reason a client goes down (i.e. connection problems), the server keeps announcing that the client is still there, although we can see there is no speed variations, which happens with connected clients. I'm not sure if this is the only case where this happens, I need some further testing. As I'm thinking, it should be possible to implement a solution where the server checks client connectivity from time to time, and if the client doesn't answer within a period of time, it would be removed from the list and it's current WU would be redirected to some other host (or marked as "undone"). Can this be done?
As a side request, is there a way to compile the source on 32-bit Linux systems? Do you know of some guides that could help me do this? Since I'm thinking on using a 32-bit system to run in serveronly mode, limitations with rainbow tables shouldn't be a problem.
Thanks in advance!
Cheers!
