Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Bittorrent (Was: RE: [HACKERS] [SUGGESTION] CVSync )
Date: Mon, 27 Mar 2006 09:15:23 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA351D9@algol.sollentuna.se>
Thread-Topic: Bittorrent (Was: RE: [HACKERS] [SUGGESTION] CVSync )
Thread-Index: AcZRIru+AwtSXWjxRHG3MJQMhwzhvwAStWAw
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Marc G. Fournier" <scrappy@postgresql.org>
Cc: <pgsql-www@postgresql.org>

> > [moved to -www]
> >
> >> Does anyone here know how to use the latest version of Bittorrent,=20
> >> from a server vs client, perspective?  The one we are currently=20
> >> running is *ancient*, and I'd like to get that vServer=20
> upgraded and=20
> >> off the templates, but without someone that knows how to setup the=20
> >> newer bittorrent, well, that's just a scary proposition ;(
> >
> > Ancient is a bit strong - it's about a year old. By that=20
> definition,=20
> > there's a whole lot of things that are a lot worse off on=20
> our servers.
> >
> > That said, it's not good. But the fact that something=20
> changed on the=20
> > box that caused it to stop working in the past couple of=20
> days can't be=20
> > because of the version, since we've been running that version for a=20
> > year.
>=20
> 'k, I looked at the server based on your report, and=20
> everything looks fine ... so, can you let me know how to=20
> reproduce the problem you are seeing?

It's automatically reproduced every 10 minutes. There are two
possibilities:
1) The python processes has started crashing. I don't think so, because
the count keeps going up.
2) They are no longer reported in a way that Proc::ProcessTable can
read. See the code at
http://gborg.postgresql.org/cgi-bin/cvsweb.cgi/portal/tools/bt/updatetor
rents.pl?rev=3D1.8;cvsroot=3Dpgweb for what we're trying to do. It is
*possible* this is done because the processes are swapped out, though I
*think* I tested the code and it handled that.


> > As for migrating it to a differnt vserver - just make sure=20
> you have a=20
> > "close enough" version of python, and it should be no=20
> problem to just=20
> > tar up the whole directory and move it over. I wouldn't be=20
> > particularly worried about that part.
>=20
> tar up what directory?  its the bittorrent binaries that I'm=20
> concerned about ... at some point, they merged all the=20
> various "utilities" into one 'bittorrent' script ... there is=20
> no longer a 'btlaunchmany.py' script, for instance ...

Tar up /usr/local/www/bt.postgresql.org.
There are no "bittorrent binaries", they are all python scripts. And
they live under taht directory along with all our utility scripts.


> And not sure what you are talking about concerning 'a year',=20
> but bittorrent was originally installed back in Nov of '03,=20
> according to the file stamps:
>=20
> # ls -lt bt*
> -rw-r--r--  1 root  wheel  5833 Nov 24  2003 btmakemetafile.pyc
> -rw-r--r--  1 root  wheel  6385 Nov 15  2003 btdownloadheadless.pyc

Where are you looking? That's before I started doing the web stuff, and
I'm definitly the one who put in what's tyhere now.

svr4# pwd
/usr/local/www/bt.postgresql.org/auto/bt
svr4# ls -l
total 154
drwxr-xr-x  4 bt    robot    1024 Mar 24  2005 BitTorrent-4.0.1
-rw-r--r--  1 bt    wheel  154427 Mar 25  2005 BitTorrent-4.0.1.tar.gz
lrwxr-xr-x  1 root  wheel      16 Apr 11  2005 bt -> BitTorrent-4.0.1


(Meaning I may be responsible for the weird groupid usded there :-P)

//Magnus