1 # The directory that overview will be stored in (the DB_HOME directory)
2 # is set in inn.conf with the 'pathoverview' option. Other parameters
3 # for tuning ovdb are in this file.
5 # Size of the memory pool cache, in Kilobytes. The cache will have a
6 # backing store file in the DB directory which will be at least as big.
7 # In general, the bigger the cache, the better. Use C<ovdb_stat -m> to see
8 # cache hit percentages. If they're less than 80%, try increasing the
9 # cache size. To make a change of this parameter take effect, shut down
10 # and restart INN (be sure to kill all of the nnrpds when shutting down).
11 # Default is 8000, which is adequate for small to medium sized servers.
12 # Large servers will probably need at least 14000.
15 # Overview data is split between this many files. Currently,
16 # innd will keep all of the files open, so don't set this too high
17 # or innd may run out of file descriptors. The nnrpds only open one
18 # at a time, regardless. May be set to one, or just a few, but only
19 # do that if your OS supports large (>2G) files. Changing this
20 # parameter has no effect on an already-established database.
23 # If txn_nosync is set to false, BerkeleyDB flushes the log after every
24 # transaction. This minimizes the number of transactions that may be
25 # lost in the event of a crash, but results in significantly degraded
26 # performance. Default is true.
29 # If useshm is set to true, BerkeleyDB will use shared memory instead
30 # of mmap for its environment regions (cache, lock, etc). With some
31 # platforms, this may improve performance. Default is false.
32 # This parameter is ignored if you have BerkeleyDB 2.x
35 # Sets the shared memory key used by BerkeleyDB when 'useshm' is true.
36 # BerkeleyDB will create several (usually 5) shared memory segments,
37 # using sequentially numbered keys starting with 'shmkey'.
38 # Choose a key that does not conflict with any existing shared memory
39 # segments on your system. Default is 6400. This parameter is only
40 # used with BerkeleyDB 3.1 or newer.
43 # Sets the page size for the DB files (in bytes). Must be a power of 2.
44 # Best choices are 4096 or 8192. The default is 8192.
45 # Changing this parameter has no effect on an already-established database.
48 # Sets the minimum number of keys per page. See the BerkeleyDB
49 # documentation for more info. Default is based on page size:
51 # default_minkey = MAX(2, pagesize / 2048 - 1)
53 # The lowest allowed minkey is 2. Setting minkey higher than the
54 # default is not recommended, as it will cause the databases to have
55 # a lot of overflow pages.
56 # Changing this parameter has no effect on an already-established database.
59 # Sets the BerkeleyDB "lk_max" parameter, which is the maxmium number
60 # of locks that can exist in the database at the same time. Default
64 # The nocompact parameter affects expireover's behavior. The expireover
65 # function in ovdb can do its job in one of two ways: By simply deleting
66 # expired records from the database; or by re-writing the overview records
67 # into a different location leaving out the expired records. The first
68 # method is faster, but it leaves 'holes' that result in space that can
69 # not immediately be reused. The second method 'compacts' the records
72 # If this parameter is set to 0, expireover will compact all newsgroups;
73 # if set to 1, expireover will not compact any newsgroups; and if set to
74 # a value greater than one, expireover will only compact groups that
75 # have less than that number of articles. Default is 1000.
77 # Experience has shown that compacting has minimal effect (other than
78 # making expireover take longer) so the default is now 1. This parameter
79 # will probably be removed in the future.
82 # Normally, each nnrpd process directly accesses the BerkeleyDB environment.
83 # The process of attaching to the database (and detaching when finished) is
84 # fairly expensive, and can result in high loads in situations when there are
85 # lots of reader connections of relatively short duration.
87 # When the readserver parameter is "true", the nnrpds will access overview
88 # via a helper server (ovdb_server -- which is started by ovdb_init).
92 # This parameter is only used when 'readserver' is true. It sets the number
93 # of ovdb_server processes. As each ovdb_server can process only one
94 # transaction at a time, running more servers can improve reader response
95 # times. Default is 5.
98 # This parameter is only used when 'readserver' is true. It sets a maximum
99 # number of readers that a given ovdb_server process will serve at one time.
100 # This means the maximum number of readers for all of the ovdb_server
101 # processes is (numrsprocs * maxrsconn). Default is 0, which means an
102 # umlimited number of connections is allowed.