BitTorrent client compiled

[MickJT]

I have compiled ctorrent, a console bittorrent client.
It works fine.

If anyone's interested I can post a "temporary" URL to it, otherwise it will appear on aminet when it next updates.

[Edit] Ok 28 views. I've come to the conclusion that there must be plenty of people without an account here not willing to create one. I've put it on http://yam.boing.net/ctorrent-1.3.2.lha

[MickJT]

> * Inability to limit upload (totally locks your connection, means download will be throttled)

While it's true that you can't limit your upload, it doesn't seem to take over downloading, here.
The official client can't limit uploads either.

> * Instability - locks the machine randomly after some hours

I've ran this for hours, perhaps they forgot the -C cache size argument, and it drained their memory after getting a certain number of pieces.

> * High CPU use (NOT recommended for real 68k machines!)

It doesn't use too much cpu (except for the file hash checking when you need to resume something).

> And of course, with real Amigas you'll probably lack the CPU power to play anything you download anyway, so in my opinion it's of interest to Pegasos and Amithlon owners only at present. Those with very large upload bandwidths...

Some people have their Amiga and not their PC, on the net, like me.
... and 68k Amigas play music fine, if that's what your gonna be download.

However i'm not advocating downloading illegal music.

[MickJT]

> You can get your whole download bandwidth by limiting upload; if you don't, you get maybe a quarter, and your internet connection is practically useless until you break ctorrent. It's even worse with routers and cable/DSL connections.

Fair enough. Still, that's the way ctorrent does things. For me it's not a reason not to put it on Aminet.

> As for not limiting upload, the official bittorrent version can. The --max_upload_rate argument has been present for a long, long while now.

I didn't know about that.. I haven't been able to list all the arguments by running btdownloadgui.exe without arguments, the list runs off the screen. I'll have to look them up on the net somewhere.

> No, that is not the cause, not on machines with a gigabyte of RAM. In fact we've never been able to find the cause. Could be an original ctorrent bug, could be Miami, could be ixemul, could be gcc... If it works stable for you, good; but remember don't run it on an FFS partition, just in case.

I use PFS3. It seems to be stable here, but I haven't "thoroughly" tested it. I don't want to download something huge just to test it out.

> I've heard of 70% CPU use with a MOS-native compile sometimes, on a G4! And hashing on a 68k must really, really take ages. And the TCP/IP stack must need a lot of CPU too with all the BT connections. But anyway, that's not really a problem if you don't intend to use your Amiga while it's running, so it's a moot point I suppose.

45-50% cpu on my 68040/40. It's been compiled with no special flags either. So it should work even on a 68000. Hashing does take quite a while 1.5 minutes for a 44meg file with 180 pieces.

[Edit] I forgot ctorrent uses parts of OpenSSL and OpenSSL was compiled for a 68020.

>> ... and 68k Amigas play music fine, if that's what your gonna be download.
> True, maybe you can get whole albums, but BT is for bulk downloads of 700 MB or more. Users shouldn't expect to find mp3s for it.

Well... I compile things as a hobby.