659 seems to have solved the 'Node suddenly ceases traffic'-problem. I have a node that has been up for close 120 hours now and there is till no sign of stagnation. It is serving up 13000 q/h at about 1MBit/s.
One thing though: Peer addr Send Count Send Size Receiving Messages Idle time Lifetime Thread Type ID 155.239.180.179:34467 0 0 yes 1 0 393188783 QThread-12740 Inbound 33c0b6 80.134.237.85:21321 0 0 yes 2 0 353667846 QThread-25929 Inbound 7e5c44 80.134.237.85:15291 0 0 yes 8 0 305199082 QThread-34344 Inbound 5e833f 68.82.148.48:18230 0 0 yes 1 0 270977775 QThread-36576 Inbound 514847 213.208.127.216:17565 0 0 yes 7 0 172335455 QThread-44615 Inbound 134183 64.252.121.1:34381 0 0 yes 10 0 22933808 QThread-45372 Inbound 323c46 216.15.192.235:56589 0 0 yes 2 0 42376945 QThread-42938 Inbound 13374f 134.193.75.29:3277 0 0 yes 8 0 18536034 QThread-45215 Inbound 1423d4 129.240.200.147:39076 1 147772 yes 471 0 19078844 QThread-45337 Inbound 3c54ad This is the initial entries of my ocm table. I do not like that idle-time always is zero on those connections where 'receiving' is 'yes'. It seems like the idletime is set to zero even if the connection is idle. Should it really be so, couldn't idle-time be set to indicate the time since the last packet was recieved on that connection instead?! /N _______________________________________________ Support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/mailman/listinfo/support
