[Bug 523540] Review Request: opentracker - BitTorrent Tracker

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=523540

--- Comment #50 from Romain Wartel <romain.wartel at cern.ch> 2010-04-07 05:25:23 EDT ---
(In reply to comment #47)
> Does opentracker start? It has to start, this is just a warning 

Yes, it starts properly. Except the whitelist file is not accepted by
opentracker, so no torrent can be added.

> You have to modify the configfile to add a whitelist or use the sysconfigfile.
> Both are in /etc/ packaged.

Sure - and this is done. "/foo/bar" is a generic name for our real whitelist
path, which looks more like /etc/opentracker-ipv4/whitelist.txt.

> Whitelist is a feature which is a wish of Matt Domsch to dominate and control
> and restrict the freedom of the users. 

Actually we find the whitelist option pretty useful. We plan to use opentracker
to share VM images over a large infrastructure, and we would like our tracker
to be dedicated for this purpose only.

> /foo/bar is just a fake! Just edit one of the conffiles to use the
> whitelist-feature!    

Yes, /foo/bar is obviously used here as a generic placeholder to demonstrate
the issue.

We have edited the configuration files, added a whitelist (we can reference it
with /etc/opentracker-ipv4/whitelist.txt if you prefer).

Nevertheless, although /etc/opentracker-ipv4/whitelist.txt exists, is populated
and world readable, opentracker still displays:

  Warning: Can't open accesslist file: /etc/opentracker-ipv4/whitelist.txt (but
will try to create it later, if necessary and possible).

Since the option is activated in the configuration file, but the whitelist
cannot be used, no torrent can be added to the tracker.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.