INCOMING.CONF(5) | InterNetNews Documentation | INCOMING.CONF(5) |
incoming.conf - Configuration of incoming news feeds
The file pathetc/incoming.conf consists of three types of entries: key/value, peer and group. Comments are from the hash character "#" to the end of the line. Blank lines are ignored. All key/value entries within each type must not be duplicated. Key/value entries are a keyword immediately followed by a colon, at least one blank and a value. For example:
max-connections: 10
A legal key does not contains blanks, colons, nor "#". There are three different types of values: integers, booleans, and strings. Integers are as to be expected. A boolean value is either "true" or "false" (case is significant). A string value is any other sequence of characters. If the string needs to contain whitespace, then it must be quoted with double quotes.
Peer entries look like:
peer <name> { # body }
The word "peer" is required. <name> is a label for this peer. It is any string valid as a key. The body of a peer entry contains some number of key/value entries.
Group entries look like:
group <name> { # body }
The word "group" is required. <name> is any string valid as a key. The body of a group entry contains any number of the three types of entries. So key/value pairs can be defined inside a group, and peers can be nested inside a group, and other groups can be nested inside a group. Key/value entries that are defined outside of all peer and group entries are said to be at global scope. Global key/value entries act as defaults for peers. When innd looks for a specific value in a peer entry (for example, the maximum number of connections to allow), if the value is not defined in the peer entry, then the enclosing groups are examined for the entry (starting at the closest enclosing group). If there are no enclosing groups, or the enclosing groups don't define the key/value, then the value at global scope is used. A small example could be:
# Global value applied to all peers that have no value of their own. max-connections: 5 # A peer definition. peer uunet { hostname: usenet1.uu.net } peer vixie { hostname: gw.home.vix.com max-connections: 10 # Override global value. } # A group of two peers which can open more connections than normal. group fast-sites { max-connections: 15 # Another peer. The max-connections: value from the # fast-sites group scope is used. peer data.ramona.vix.com { hostname: data.ramona.vix.com } peer bb.home.vix.com { hostname: bb.home.vix.com max-connections: 20 # He can really cook. } }
Given the above configuration file, the defined peers would have the following values for the max-connections key.
uunet 5 vixie 10 data.ramona.vix.com 15 bb.home.vix.com 20
The following keys are allowed:
Written by Fabien Tassin <fta@sofaraway.org> for InterNetNews. Converted to POD by Julien Elie.
$Id: incoming.conf.pod 10179 2017-09-18 20:13:48Z iulius $
2018-01-28 | INN 2.6.3 |