aMule Forum
English => en_Bugs => Topic started by: Supersnail on August 02, 2004, 02:56:14 PM
-
Hi,
Because I received a lot of warnings regarding my shared files when I started aMule I decided to let aMule rehash them all. So I removed the known.met file and started aMule. aMule told me there were 42 known shared files and 2352 unknown. I only had 252 files in my shared directory, if I add the 42 I'm still downloading that makes a total of 294 shared files instead of 2352.
I discovered that this is because of my categories. I have eight categories and they all place the files in the same directory as the files which don't belong to a catgory. That's why aMule was going to hash 8 * 294 = 2352 files. I have now changed my category settings so files in a category will be placed in a different directory, but I still think this might need to be changed.
Second, (you might have discovered it already, but I couldn't find it on the forum with the search function) when aMule is hashing files and when I click on the refresh button in the shared files tab the number of unknown files increases. I haven't looked at this very much, but I think aMule adds the number of files it still has to hash to the number of unknown files (so, if aMule is hashing 100 files and it's finished hashing three, when you click on the refresh tab it thinks it still has to hash 97 + 97 = 194 files).
Third, I also noticed that in preferences/directories, when I right-click on the icon in front of a directory in the 'shared directories' box I hear a lot of disk activity and when that's over aMule isn't responding anymore. The only way to get aMule to respond again is to kill and start it again.
-
So, anyone wants to say something about this?
-
Right. Thanks for pointing this out. I'm working on it, but you'll have to wait for a more verbose reply till tomorrow. G'nite. ;)
-
Ok, I'll address the 3 issues:
1) This because there wasn't any checks for duplicate files on the hashing queue.
2) Same as 1.
3) Right-clicking shares recursivly, so if you share a dir at a low point, it'd take a _long_ time. This behavoir is silly and will be changed to a popup-menu. ;)
-
This because there wasn't any checks for duplicate files on the hashing queue.
Ok, I already had that impression. I suppose this will be changed in a next version?
-
Xaiganr already fixed it in current CVS. Wait for the nightly CVS tarball at hirnriss ;-)
Greetings!
-
Ok, even better.