You are not logged in.
It's something totally completely incomprehensible to me.
I reintalled Arch a while ago. Made a backup of the old ~/.mldonkey. Now I retored them to where they belong.
$ mv ~/backup/mldonkey/donkey.ini ~/.mldonkey/
$ mv ~/backup/mldonkey/stat* ~/.mldonkey/
$ mv ~/backup/mldonkey/temp/* ~/.mldonkey/temp/
Then I started mldonkey with the telnet interface. I saw the old download which was not completed. I added a new one to download. The new one was small and quickly got done. Here comes the nuts:
$ ls ~/.mldonkey/incoming/files/ #WTF?! Nothing?
$ ls ~/backup/mldonkey/incoming/files/ #WTH?!
Nuts.cue
I also discovered the temp files all went to ~/backup/mldonkey/temp/, not ~/.mldonkey/temp.
That is damn strange! I killed the mldonkey daemon. mv ~/.mldonkey ~/Nuts so ~/.mldonkey doesn't even exist now!
Fire up mldonkey again. It's working. like nothing happened. All it's doing it take ~/backup/mldonkey as if it were ~/.mldonkey.
How is this possible? It's acting like a smart ass which I definitely hate!
I'm in serious faint now. Seriously.
This silver ladybug at line 28...
Offline
Hello lolilolicon!
If you install now a new one, can mldonkey work so ? If yes, you can compare them (older-newer one), with vim ~/backup/mldonkey -c 'vert diffsplit ~/,mldonkey' or with your favourite diff application.
Offline