aMule Forum
English => Multiplatform => Mac OSX => Topic started by: m2kio on March 18, 2005, 05:45:06 PM
-
hi,
i have not yet seen a complaint in the 'general' bug area, so it might be Mac specific:
with this version i experience weird ul credits from some peers: right now i have more than 5 peers (out of 300) which claim more than 1 GB credit volume (top is approx. 3.5GB) and getting high priority as a result. this is at least unlikely, if not entirely impossible.
... m2kio !
-
hmm... there might be something to it. it's a bit hard for me to tell because i have a number of clients that have up- and down-values of multiple gb because i load and share a lot of stuff from a particular community.
but then i also noticed a number of clients that dowloaded 3-4gb from me and gave between 0 and 20mb. i have a feeling that something with these clients is not ok, particularly since i don't recognize most of their nicks.
ok, i just found another thing that looks really suspicious: i have about 100 clients listed who each got at least 2gb from me, but the stats show me a total upload of only 70gb. so there must be something wrong here.
just checked the log and the first message is "Creditfile loaded, 5646 clients are known - Credits expired for 1923 clients!". seems like a large number of purges at startup but i haven't looked at this more systematically.
-
It's rather strange problem. Can you try to remove your clients.met files and report of you get any strange entries still?
-
To elaborate a bit. My own clients.met file was broken, but removing it and running aMule for a brief while seemed to produce only valid entries. I'll be looking out to see if it breaks again.
-
Originally posted by Xaignar
It's rather strange problem. Can you try to remove your clients.met files and report of you get any strange entries still?
hi,
i succeeded in removing it. what's next? :D
ok, i'll post an update next week, but i'm currently not dl'ing, so it might be not fully significant.
maybe there should be a check for broken clients.met?
... m2kio !
-
There already is (based on the saved keysize, which has a known limit), however, I can't see how would I could detected bad up/down values.