aMule Forum
English => en_Bugs => Topic started by: GhePeU on May 03, 2004, 01:11:44 PM
-
If I rename a shared file (adding or removing 0, changing extension), the file is no more showed on shared files list
for example, I renamed file XYZ.N.01.rar in XYZ.N.001.rar and this is console output after I reload file to make amule hash the new one:
Sharing //path/to/the/file/directory//XYZ.N.001.rar
Finished Hashing XYZ.N.001.rar
XYZ.N.001.rar is already on list, not added
The Found file: XYZ.N.01.rar
1: 1083507572 36848030
2: 1083507572 36848030
but XYZ.N.01.rar isn't in list, and neither XYZ.N.001.rar is
On Amule log I can read "Found 127 known shared files, 1 unknown"
this bug occurred for 7-8 files and I had to remove known.met and let amule rehash everything
-
I second this behaviour, though it happened to me without renaming files. Some files were rehashed on every reload/restart of aMule, with output of "Found 392 known files, 3 unkown". Those hashed files weren't added to the Shared Files list after hashing. A recreation of knownfiles.met solved this bug for me.
-
thanky guys
-
same bug when moving a file from incoming folder to another folder
i downloaded a file named XYZ.[4.di.13].by.jkwxyz.rar, moved from Incoming Folder to another shared directory, renamed XYZ.[04.di.13].rar and the file is not in shared files list
When I restart amule output tells:Sharing //path/to/a/shared/directory//XYZ.[04.di.13].rar
Finished Hashing XYZ.[04.di.13].rar
Hashing thread timed out with no aditions - removing thread
Hashing thread ended
-
This problem happens whenever a shared file is "touched". It has been filed as SHRD.3 bug.
Thanks for all those reports :-)
Greetings.