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

NAME

6       ovdb_stat - Display information from the ovdb database
7

SYNOPSIS

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

DESCRIPTION

14       ovdb_stat displays information from the ovdb database:  Berkeley DB
15       statistics, newsgroup data, and overview records.  The output can
16       optionally be in HTML format.
17

OPTIONS

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

WARNINGS

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

HISTORY

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

SEE ALSO

69       ovdb(5).
70
71
72
73INN 2.6.5                         2022-01-23                      OVDB_STAT(8)
Impressum