| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
RTFM! |
| 5 |
|
| 6 |
"You can prevent other people from using your tracker--as postgresql.org |
| 7 |
does, by the way--by telling bttrack to track only those torrents of |
| 8 |
which it has copies in a user-defined directory. For example, if I place |
| 9 |
a copy of the pg_live torrent file in a directory where bttrack can see |
| 10 |
it, it will limit the tracker to file sharing for just pg_live. That's |
| 11 |
the purpose of the --show_names and --allowed_dir switches: |
| 12 |
|
| 13 |
$ bttrack --port 8099 --show_names 1 --allowed_dir ~/mytorrents \ |
| 14 |
--dfile downloadinfo.txt" |
| 15 |
|
| 16 |
DOH! |
| 17 |
|
| 18 |
Also found that mod_bt can be used as a tracker with apache handling the |
| 19 |
access rights and everything else. |
| 20 |
|
| 21 |
|
| 22 |
Antoine Martin wrote: |
| 23 |
> Hi list, |
| 24 |
> |
| 25 |
> I am looking for an easy-to-setup bittorrent tracker for a small list of |
| 26 |
> large files that I manage. |
| 27 |
> I found some good/comprehensive instructions here: |
| 28 |
> http://www.linuxdevcenter.com/lpt/a/6153 |
| 29 |
> But unfortunately this means that the tracker can be used by anyone to |
| 30 |
> track new torrents, and this is not acceptable for my purpose. |
| 31 |
> Can anyone recommend a bittorrent tracker which restricts adding new |
| 32 |
> torrents using some kind of authentication or server-side management system? |
| 33 |
> |
| 34 |
> Thanks |
| 35 |
> Antoine |
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
Version: GnuPG v1.4.9 (GNU/Linux) |
| 38 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 39 |
|
| 40 |
iEYEAREKAAYFAkl8GPMACgkQGK2zHPGK1rv1+QCcDKvXHw6ewFljFiX/eSgUqHB1 |
| 41 |
Bg4An1/zJpx+4fxoOGLwTTxEeyLpGJgy |
| 42 |
=Hifm |
| 43 |
-----END PGP SIGNATURE----- |
Archives