1OVDB_STAT(8)              InterNetNews Documentation              OVDB_STAT(8)
2
3
4

NAME

6       ovdb_stat - Display information from the ovdb database
7

SYNOPSYS

9       ovdb_stat -Hgci [-r artnumrange] newsgroup [newsgroup ...]
10
11       ovdb_stat -Hklmtv [-d database]
12

DESCRIPTION

14       ovdb_stat displays information from the ovdb database: BerkeleyDB sta‐
15       tistics, newsgroup data, and overview records; and optionally outputs
16       in HTML format.
17

OPTIONS

19       -g  Newsgroup himark, lowmark, article count, and flag for the given
20           newsgroups (as stored in the ovdb "groupinfo" database) are dis‐
21           played.
22
23       -c  Similar to -g, except the himark, lowmark, and count are calculated
24           by actually scanning the overview records and counting them.  This
25           can be a lengthy operation on groups with lots of articles.
26
27       -i  Internal data regarding the given newsgroups are displayed.
28
29       -r artnumrange
30           Overview records are retrieved.  The artnumrange parameter may be a
31           single article number, or a range of articles in the format
32           "low-hi".
33
34       -H  Output is presented in HTML format.
35
36       -k  Displays lock region statistics, as returned by the BerkeleyDB
37           lock_stat() call.
38
39       -l  Displays log region statistics, as returned by the BerkeleyDB
40           log_stat() call.
41
42       -m  Displays global memory pool statistics, as returned by the Berke‐
43           leyDB memp_stat() call.
44
45       -M  Same as -m, and also displays memory pool statistics for each data‐
46           base file.
47
48       -t  Displays log region statistics, as returned by the BerkeleyDB
49           txn_stat() call.
50
51       -v  Displays ovdb version, and BerkeleyDB version.
52
53       -d database
54           Displays information about the given database, as returned by the
55           BerkeleyDB db->stat() call.  This operation may take a long time on
56           busy systems (several minutes or more).
57

WARNINGS

59       ovdb_stat may be safely killed with the INT, TERM, or HUP signals.  It
60       catches those signals and exits cleanly.  Do not kill ovdb_stat with
61       other signals, unless absolutely necessary, because it may leave stale
62       locks in the DB environment.
63

HISTORY

65       Written by Heath Kehoe <hakehoe@avalon.net> for InterNetNews.
66

SEE ALSO

68       ovdb(5)
69
70
71
72INN 2.4.0                         2002-02-02                      OVDB_STAT(8)
Impressum