On Thu, 23 Jun 2005, Tim Hammerquist wrote:
Mark C. Ballew wrote:
One suggestion I'd like to toss in is that you shouldn't run multiple
btdownloadcurses instances. The issue is that, while two or three
copies isn't bad, four or more starts to eat up a lot of memory and
CPU time. As someone who always something on the "bt-burner"
downloading, I use btlaunchmanycurses.
Put in the .torrent's in question into a staging directory. I call
mine "btbatch". Start btlaunchmanycurses with what ever arguements you
usually use and the location of btbatch. When a torrent finishes,
simply remove the .torrent file and btlaunchmany will remove the
download from it's queue. To add more torrents, just copy them into
the btbatch directory and they'll be picked up.
I looked at btlaunchmanycurses, and it looked pretty cool, but the
manpage and documentation are severely lacking. So maybe you can answer
my question:
I know that you can add torrent files to the directory at runtime and
btlaunchmany* will periodically rescan the directory for new torrents
and, if found, add them. But if you remove a .torrent from the
directory, will it stop seeding the torrent? Or do I have to kill the
whole session to stop seeding the latest gentoo/sarge iso?
It stops seeding the download as soon as you remove the torrent file from
the directory. Err... as soon as it detects the missing file.
I use this same technique to download and it has worked well for me. I
haven't had issues with memory consumption in the latest versions of the
bittorrent client though. I've done over 15 simultaneous downloads with
the btlaunchmanycurses client and had no issues, so perhaps they thinned
it down a bit. The older clients would lock my machine after a while
though.
- Sebastian
_______________________________________________
RLUG mailing list
[email protected]
http://lists.rlug.org/mailman/listinfo/rlug
