On 8/23/2013 8:57 AM, n0jy wrote:
Has anyone any input on the CPU usage of the D-RATS application, mine
starts out all happy but after some time (appears to be a few hours, I
haven't actually clocked it yet)
It is a known bug. If the connection to a ratflector is lost for any reason, d-rats goes into this CPU loop condition.
Sometimes this is caused by a network provider killing idle sessions, in which case setting up a beacon every few minutes will hide this bug.
Regards,
-John
