ovdb_init(8)

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

NAME

6       ovdb_init - Prepare ovdb database for use
7

SYNOPSYS

9       ovdb_init ["-u"⎪"-r"]
10

DESCRIPTION

12       This command must be run before any other process can access the over‐
13       view database.  It performs the following steps:
14
15       1   Creates the database environment, if necessary
16
17       2   If the database is idle (and if the "-u" option is not specified),
18           it performs a normal recovery.  The recovery will remove stale
19           locks, recreate the memory pool cache, and repair any damage caused
20           by a system crash or improper shutdown.
21
22       3   If the "-u" option is specified, it performs any necessary upgrades
23           to the database.  See the UPGRADING section below.
24
25       4   Starts the DB housekeeping processes (ovdb_monitor) if they're not
26           already running. (Unless the "-r" option is specified).
27
28       5   Starts the ovdb readserver (ovdb_server) processes if "readserver"
29           in ovdb.conf is "true", and if they're not already running. (Unless
30           the "-r" option is specified).
31
32       Returns exit status of 0 if all steps were completed successfully.  In
33       the event of an error, messages are written to syslog and/or stderr.
34
35       If a recovery was attempted but it failed, the database may be damaged
36       beyond repair, requiring a rebuild with makehistory(8).
37
38       This command is normally invoked automatically by rc.news(8).
39
40       It is OK to run this command multiple times.
41

OPTIONS

43       "-r"
44           Perform recovery only.  "ovdb_monitor" is not started.
45
46       "-u"
47           Perform any needed upgrades.  Recovery is not attempted.
48           "ovdb_monitor" is started if the upgrade succeeded.
49

UPGRADING

51       There are two situations in which the database will need to be
52       upgraded:
53
54       ·   You upgrade the BerkeleyDB library to a newer version, for example
55           from 2.7.7 to 3.1.17.  In this case, the BerkeleyDB db->upgrade()
56           method is used.
57
58       ·   You upgrade ovdb to a newer major version; i.e., ovdb-1.0 to
59           ovdb-2.0.
60
61       In both of these cases, the database is upgraded in-place; and the
62       upgrade can not be undone.  Do not interrupt the upgrade process once
63       it has started, because there is a risk of irrepairable corruption.
64       The upgrade may take several minutes to complete.  If an upgrade does
65       get interrupted, try running the upgrade again.
66
67       Here's an example procedure to upgrade a database created with Berke‐
68       leyDB 2.7.7 to use BerkeleyDB 3.1.17:
69
70       1   Build and install the BerkeleyDB 3.1.17
71
72       2   Run configure in the INN source tree and make sure it picks up the
73           right BerkeleyDB directory (e.g., /usr/local/BerkeleyDB.3.1)
74
75       3   Do a "make"
76
77       4   Shut down INN (e.g., with "rc.news stop").  Be sure to kill all
78           nnrpds as well.
79
80       5   Do a "make update" to install the new binaries.
81
82       6   Run "ovdb_init -u" as the news user.
83
84       7   Start INN with "rc.news"
85
86       It is OK to specify "-u" even if no upgrades are needed.
87

HISTORY

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

NAME

SYNOPSYS

DESCRIPTION

OPTIONS

UPGRADING

HISTORY

SEE ALSO