steeler359's Journal: amule and amuled

Well, work's not too hectic at the moment, so I thought I'd get a few JE's knocked off while I had a chance.

The trusty P-III upstairs has recently taken on ed2k duties at the Steele household. I'll get round to writing about this at some point, but it used to be Win2k server running emule, and now it's FC5 and it's running...aMule. Emule itself is open source, and probably the most-used successor of the original eDonkey 2000 client. I've been running it for years on low-end hardware with Win2k and it's hardly ever done me wrong. Actually I've been using Emule Plus, but there's very little difference, AFAIK...

This software seems pretty neat. You have to install WxWidgets (whatever they may be), to get it to work, but this didn't present a challenge to me on FC5.

Now, I used to run Emule 24x7 on the Win2k box in a Terminal Services session, and this worked pretty well. I used to need to log in to add ed2k links and, After my failed attempts at getting bandwidth shaping to work, throttle back the bandwidth when my wife wanted to web browse (chuckle). After a couple of weeks of using Amule in FreeNX, I just wasn't geting the same experience. Suspending the session more often than not seemed to cause amule to just stop downloading (though this could have been my imagination), and it was pretty unresponsive (probably more to do with the old hardware it's running on than anything else).

Enter amuled. This is, as the name suggests, a lovely little bit of software from the developer of amule which is simply amule without a GUI. There's a few tricks to getting it working though, hence this JE...

Assuming you've got amuled running, and have tried amulecmd (the CLI tool for amuled), and amuleGUI and/or amuleweb without success

Make sure the following is present in your ~/.aMule/amule.conf and your ~/.aMule/remote.conf for good measure:

ECUseTCPPort=1

You may have to create this line, or set 0 to 1, as apparently Unix sockets are not working in this release (2.1.3). So use good ol' TCP/IP...

Next, enter the md5sum of the password, there's a way to do this on the command line, but I don't have it to hand at the moment. Enter this as:

Password=b43555325d34534340534e435

That's not my actual password hash, BTW :)

With these two bits in place, it should be possible to connect to amuled via amulecmd, amulegui and amuleweb. I found this info tucked away on a forum somewehere, so hopefully, this will help it reach a wider audience.

Goodnight and Good luck :)