Provided by: inn2_2.4.2-3ubuntu1_i386 bug

NAME

       ovdb_stat - Display information from the ovdb database

SYNOPSYS

       ovdb_stat -Hgci [-r artnumrange] newsgroup [newsgroup ...]

       ovdb_stat -Hklmtv [-d database]

DESCRIPTION

       ovdb_stat displays information from the ovdb database: BerkeleyDB
       statistics, newsgroup data, and overview records; and optionally
       outputs in HTML format.

OPTIONS

       -g  Newsgroup himark, lowmark, article count, and flag for the given
           newsgroups (as stored in the ovdb "groupinfo" database) are
           displayed.

       -c  Similar to -g, except the himark, lowmark, and count are calculated
           by actually scanning the overview records and counting them.  This
           can be a lengthy operation on groups with lots of articles.

       -i  Internal data regarding the given newsgroups are displayed.

       -r artnumrange
           Overview records are retrieved.  The artnumrange parameter may be a
           single article number, or a range of articles in the format
           "low-hi".

       -H  Output is presented in HTML format.

       -k  Displays lock region statistics, as returned by the BerkeleyDB
           lock_stat() call.

       -l  Displays log region statistics, as returned by the BerkeleyDB
           log_stat() call.

       -m  Displays global memory pool statistics, as returned by the
           BerkeleyDB memp_stat() call.

       -M  Same as -m, and also displays memory pool statistics for each
           database file.

       -t  Displays log region statistics, as returned by the BerkeleyDB
           txn_stat() call.

       -v  Displays ovdb version, and BerkeleyDB version.

       -d database
           Displays information about the given database, as returned by the
           BerkeleyDB db->stat() call.  This operation may take a long time on
           busy systems (several minutes or more).

WARNINGS

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

HISTORY

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

SEE ALSO

       ovdb(5)