the forums at degreez.net

Alright, so I got a server with like 5 GB of space and a kick ass connection that I want to use to help seed my torrents. But, I have a few questions that hopefully someone can answer...

1. Are these global or on a per torrent basis?
   
   
   Code:
   $GLOBALS["max_upload_rate"] = 50000 ;
   $GLOBALS["max_uploads"] = 2 ;
2. Don't I have to like run a cronjob or something? I mean how does the seeding process begin and run?
   
3. Does the script keep statistics? I'd like to see if it's actually working, how many people downloaded off it, how many MB/GB it's uploaded, etc.

Thanks in advance and I hope this was the right place to ask....

That's my cue.

1. They're global.
2. The script is a real web script. It needs no cron and no shell access. What you might be confusing it for is something that actually interacts with the clients like a normal peer. It does not.
3. Some rudimentary byte counts are kept in the database, but there's no script to view them. You'll probably have to use phpMyAdmin to view them. It's stored in the `phpseed_speedlimit` table.

So it automatically does it's thing? Cool.

Thanks again.

Well, actually, mind explaining how it works?

My best guess is that on torrent submit, it sends a notice to the tracker that it's seeding. The tracker then gives out the URL to the seeding script to the clients who connect to the server and download off it. Or am I way off?

Also, what's the CPU usage like on this script? Is it barely noticable or pretty heavy? Don't want the host getting pissed with CPU usage...

----------------------------------------------------------------------------------------------------

*EDIT* - Just saw this thread:

http://forums.degreez.net/viewtopic.php?t=32

Off to read that to see if it answers my questions.

----------------------------------------------------------------------------------------------------

*EDIT #2*

Okay, so I get how it works. You need to edit the .torrent file to contain a link to the seed.php file on the seeder and any client that has support for this will know to go get it off the HTTP server as well.

Too bad it doesn't make the tracker aware of it's self, but then again, I don't see a way for that to work as the tracker only stores the seed's IP AFAIK and that wouldn't do much good unless I had a dedicated server.

Well, better than nothing. Now off to experiment with a dummy .torrent.

My guide to webseeding ... http://bittorrent.radlight.com/webseeding.htm