public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: [email protected]
Subject: Re: Bittorrent (Was: RE: [HACKERS] [SUGGESTION] CVSync )
Date: Sun, 26 Mar 2006 21:13:51 +0200
Message-ID: <[email protected]> (raw)
[moved to -www]
> Does anyone here know how to use the latest version of
> Bittorrent, from a server vs client, perspective? The one we
> are currently running is *ancient*, and I'd like to get that
> vServer upgraded and off the templates, but without someone
> that knows how to setup the newer bittorrent, well, that's
> just a scary proposition ;(
Ancient is a bit strong - it's about a year old. By that definition,
there's a whole lot of things that are a lot worse off on our servers.
That said, it's not good. But the fact that something changed on the box
that caused it to stop working in the past couple of days can't be
because of the version, since we've been running that version for a
year.
Moving on, some figures: In the active log now, we have about 4 million
FTP downloads and 190,000 bittorrent downloads. Meaning bittorrent is
only ~ 5% of our downloads. OTOH 190,000 downloads since Jan 11th, 2005
is still more than 400 downloads per day...
But the bottom line of that reasoning is, how much time do we want to
spend hacking around the bittorrent stuff? We're better off now than
before we had an automated system, but is it really something the end
user wants. (For example, we don't know how many of those hits are hits
by search engines and mirroring scripts - that could easily be a couple
of hundreds aday..)
As for migrating it to a differnt vserver - just make sure you have a
"close enough" version of python, and it should be no problem to just
tar up the whole directory and move it over. I wouldn't be particularly
worried about that part.
//Magnus
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Bittorrent (Was: RE: [HACKERS] [SUGGESTION] CVSync )
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox