diff options
Diffstat (limited to 'opentracker.conf.sample')
-rw-r--r-- | opentracker.conf.sample | 52 |
1 files changed, 50 insertions, 2 deletions
diff --git a/opentracker.conf.sample b/opentracker.conf.sample index db45122..054e405 100644 --- a/opentracker.conf.sample +++ b/opentracker.conf.sample | |||
@@ -2,7 +2,7 @@ | |||
2 | # | 2 | # |
3 | 3 | ||
4 | # I) Address opentracker will listen on, using both, tcp AND udp family | 4 | # I) Address opentracker will listen on, using both, tcp AND udp family |
5 | # (note, that port 6969 is implicite if ommitted). | 5 | # (note, that port 6969 is implicit if omitted). |
6 | # | 6 | # |
7 | # If no listen option is given (here or on the command line), opentracker | 7 | # If no listen option is given (here or on the command line), opentracker |
8 | # listens on 0.0.0.0:6969 tcp and udp. | 8 | # listens on 0.0.0.0:6969 tcp and udp. |
@@ -44,17 +44,65 @@ | |||
44 | # listing, so choose one of those options at compile time. File format | 44 | # listing, so choose one of those options at compile time. File format |
45 | # is straight forward: "<hex info hash>\n<hex info hash>\n..." | 45 | # is straight forward: "<hex info hash>\n<hex info hash>\n..." |
46 | # | 46 | # |
47 | # IIa) You can enable dynamic changesets to accesslists by enabling | ||
48 | # WANT_DYNAMIC_ACCESSLIST. | ||
49 | # | ||
50 | # The suggested way to work with dynamic changeset lists is to keep a | ||
51 | # main accesslist file that is loaded when opentracker (re)starts and | ||
52 | # reloaded infrequently (hourly or daily). | ||
53 | # | ||
54 | # All changes to the accesslist (e.g. from a web frontend) should be | ||
55 | # both appended to or removed from that file and sent to opentracker. By | ||
56 | # keeping dynamic changeset lists, you can avoid reloading huge | ||
57 | # accesslists whenever just a single entry is added or removed. | ||
58 | # | ||
59 | # Any info_hash (format see above) written to the fifo_add file will be | ||
60 | # kept on a dynamic add-changeset, removed from the dynamic | ||
61 | # delete-changeset and treated as if it was in the main accesslist file. | ||
62 | # The semantic of the respective dynamic changeset depends on whether | ||
63 | # WANT_ACCESSLIST_WHITE or WANT_ACCESSLIST_BLACK is enabled. | ||
64 | # | ||
65 | # access.fifo_add /var/run/opentracker/adder.fifo | ||
66 | # | ||
67 | # Any info_hash (format see above) written to the fifo_delete file will | ||
68 | # be kept on a dynamic delete-changeset, removed from the dynamic | ||
69 | # add-changeset and treated as if it was not in the main accesslist | ||
70 | # file. | ||
71 | # | ||
72 | # access.fifo_delete /var/run/opentracker/deleter.fifo | ||
73 | # | ||
74 | # If you reload the accesslist by sending SIGHUP to the tracker process, | ||
75 | # the dynamic lists are flushed, as opentracker assumes thoses lists are | ||
76 | # merged into the main accesslist. | ||
77 | # | ||
78 | # NOTE: While you can have multiple writers sending lines to the fifos, | ||
79 | # any writes larger than PIPE_BUF (see your limits.h, minimally 512 | ||
80 | # bytes but usually 4096) may be interleaved with data sent by other | ||
81 | # writers. This can lead to unparsable lines of info_hashes. | ||
82 | # | ||
83 | # IIb) | ||
47 | # If you do not want to grant anyone access to your stats, enable the | 84 | # If you do not want to grant anyone access to your stats, enable the |
48 | # WANT_RESTRICT_STATS option in Makefile and bless the ip addresses | 85 | # WANT_RESTRICT_STATS option in Makefile and bless the ip addresses |
49 | # allowed to fetch stats here. | 86 | # or network allowed to fetch stats here. |
50 | # | 87 | # |
51 | # access.stats 192.168.0.23 | 88 | # access.stats 192.168.0.23 |
89 | # access.stats 10.1.1.23 | ||
52 | # | 90 | # |
53 | # There is another way of hiding your stats. You can obfuscate the path | 91 | # There is another way of hiding your stats. You can obfuscate the path |
54 | # to them. Normally it is located at /stats but you can configure it to | 92 | # to them. Normally it is located at /stats but you can configure it to |
55 | # appear anywhere on your tracker. | 93 | # appear anywhere on your tracker. |
56 | # | 94 | # |
57 | # access.stats_path stats | 95 | # access.stats_path stats |
96 | # | ||
97 | # II | ||
98 | # If opentracker lives behind one or multiple reverse proxies, | ||
99 | # every http connection appears to come from these proxies. In order to | ||
100 | # take the X-Forwarded-For address instead, compile opentracker with the | ||
101 | # WANT_IP_FROM_PROXY option and set your proxy addresses or networkss here. | ||
102 | # | ||
103 | # access.proxy 10.0.1.23 | ||
104 | # access.proxy 192.0.0.0/8 | ||
105 | # | ||
58 | 106 | ||
59 | # III) Live sync uses udp multicast packets to keep a cluster of opentrackers | 107 | # III) Live sync uses udp multicast packets to keep a cluster of opentrackers |
60 | # synchronized. This option tells opentracker which port to listen for | 108 | # synchronized. This option tells opentracker which port to listen for |