aMule Forum
English => aMule Help => Topic started by: mithrandir77 on November 03, 2008, 12:16:23 PM
-
Hi All,
I found that on my opensuse 11, amule starts to hash each file shared everytime it is started.
Is it a wanted behaviour? How can I disable it (if it is possibile)?
Regards,
mithrandir77
-
That's not wanted behaviour. What version are you using ? Are there any messages hinting to the cause of the problem ?
-
Hi,
I am using amule version 2.2.2, precompiled for opensuse 11 (x86_64)
(http://packman.links2linux.org/package/amule/69034)
Looking at the amule log, I don't find any useful message, only the hashing messages.
???
-
maybe amule can't write on confing files?
check them.
-
I don't find any problem in writing in config file, but I will check.
Could my problem be related to a high number of shared files (about 2000)?
-
Should not be related.
Stop amule. Delete the files known.met and known2_64.met in the .amule dir. Start amule. Wait until it finishes hashing (will take some time with 2000 files...). Stop amule again. Check the size of the two files.
-
Hi,
I tried to remove both known*.met, but it started just two times without hashing, the third one it hashed all shared files (about 2600)
???
-
Stop amule again. Check the size of the two files.
Then restart it. Does it hash again ?
-
Yes, it starts hashing other 111 files.
Now I started amuled daemon again for 2 times and it didn't hash anything.
Could it happen after each the system boot?
-
111 of 2600 is not that much. :P
Do you have something running that might change names or file dates of your shared files ? Or do you share your temp folder or something ?
-
After rebooting some times my system amule finally started to rehash all the shared files: looking at the logfile I found this first row
2008-11-05 14:48:00: KnownFileList.cpp(86): WARNING: Knownfile list corrupted, contains invalid header.
Could it be related to the timeout problem?