Installation notes are contained elsewhere, but adding the use of screen would be advisable and the use of CTCS optional. Installed :

unslung 6.8, ctorrent 1.3.4-2, enhanced-ctorrent dnh3.2-9, ctcs 1.4-8

tested on public and private trackers with high and low peer count torrents

Intitiate single new torrent with the command:

enhanced-ctorrent -C 4 -m 40 -S localhost:2780 filename.torrent

where option "-C 4" provides 4mb cache, "-m 40" sets minimum peers to 40 and "-S" sets the web interface to local port 2780 (dependant on having installed CTCS). Having played around with cache settings it seems that the slug works fastest with some ram cache allowed. The minimum peers setting is supposed to trigger an "update tracker, get more peers" function but this doesn't seem to work as designed, so this works as a default to a median number of peers for a speedy download/upload.

Upload and download rates are controlled from the CTCS web gui where they can be changed to suit, usually 10-20 kb/s less than your ISP allowance.

Some trackers do not like this client and some clients seem to have aggressive settings where the slug/dnh just doesn't get a look in. This has been compared with testing the same torrent with 3 different clients - Azureus 3.x/winxp, Rtorrent0.7/Debian and dnh3.2/unslung.

Previously, after checking the tracker connection from the command line I have then made the client switch to daemon mode but now I just use screen as there are occasions when the client hangs at cpu +95%. This seems to be related to the floating point exception noted elsewhere in the nslu2 mailing lists.

In my instance, because of my ISP, I need to be able to stop downloading during peak times and switch to just seeding a different torrent already completed. To stop the client properly you must use either the Quit command from the CTCS web gui or the command line and allow the client and tracker to complete their update properly or you will get errors in the pieces check. This is noted mainly in large torrents of 3gb (some reports at 2.5gb) and over where the client fails to properly account for pieces already downloaded, so when a new session is started and the client performs a piece check the amount verified is less than actual, to the tune of 10 to 30% less.

To seed a completed torrent use the following:

enhanced-ctorrent -C 4 -f -S localhost:2780 filename.torrent

where option "-f" forces the client into seed mode without checking for piece completion.

Notes:

Fails to properly read/write bitfield file and/or check for pieces of torrents over approx 3gb (some reports at 2.5gb).

Not favoured by many other torrent clients/trackers, so downloads will be slow whereas uploads will be nominal.

Has no global stats or multi-session stats, so user onus applies.

Not particularly aggressive at getting more peers so downloads can slow until user forces "update tracker".

While this isn't the place to discuss torrent etiquette, using this client on the unslung requires the user to be more conscious of their share ratio...

• update **

According to the ctorrent project page as of the 27th November, a bug has been spotted in the btfiles.cpp file where you can delete the "setvbuf" line and recompile. This fixes a completed torrent reporting as incomplete upon restart error. This is probably related to the bitfield error mentioned above. An updated version with this fix, enhanced-ctorrent_dnh3.2-10, is available at the Optware feeds. Simply run ipkg update and then ipkg install enhanced-ctorrent to install the latest version.