Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JPB]

Hi,

I've come across a novel issue the other day: I wanted to share some completed .avi files on the donkey/mule network, so I marked the directory in which these were held as shared in my aMule prefs. For some strange reason though, it would not hash them and would not show them in "Shared Files" view.

I checked whether restarting the 'mule would make a difference, but no luck. Had to hash these using eMule in VMWare/Windows and copy & paste the known.met file into my aMule directory - then it worked fine. This is not caused by the wrong permissions - my 'mule resides in my home directory with full read & write access; so do the files I wanted to share.

I inquired about this issue on the fileheaven forum and a couple of other users reported the same problem.

I am using aMule 2.0.0rc3 on SuSE Linux 9.1 Pro, if that is any help. Would be good to know what the solution is for future reference.

Cheers,

JPB

[Jacobo221]

Yes it is known to happen sometimes in rc2 and rc3. The best way to solve this is to remove ~/.aMule/knwon.met and let aMule hash all files again :-(
But don't worry, it will be fixed... someday ;-)
Greetings and thnks!

[JPB]

Thanks for that! Obviously this is not what you would call a *serious* issue, but it's still good to know that simply getting rid of the known.met file accomplishes the desired task. Better than having to go to a Windows version to do the hashing any day! :-)

JPB

[Jacobo221]

heh, definitly better, yes ;-)
Btw, next time, take a look at aMule common problem's FAQ at http://www.amule.org/wiki/index.php/AMule_problems
In most cases I would bet the answer is there.
Greetings!