head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.56.40; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.13; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.04; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.10.15.03.47.35; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.05.01; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB: db_checkpoint
db_checkpoint
|
 
|
db_checkpoint [-1Vv]
[-h home] [-k kbytes] [-L file] [-p min]
Description
The db_checkpoint utility is a daemon process that monitors the
database log, and periodically calls txn_checkpoint to checkpoint
it.
The options are as follows:
- -1
- Checkpoint the log once, regardless of whether or not there has been
activity since the last checkpoint and then exit.
- -h
- Specify a home directory for the database environment; by
default, the current working directory is used.
- -k
- Checkpoint the database at least as often as every kbytes of log
file are written.
- -L
- Log the execution of the db_checkpoint utility to the specified file in the
following format, where ### is the process ID, and the date
is the time the utility was started.
db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
This file will be removed if the db_checkpoint utility exits gracefully.
- -p
- Checkpoint the database at least every min minutes if there has
been any activity since the last checkpoint.
- -V
- Write the library version number to the standard output, and exit.
- -v
- Write the time of each checkpoint attempt to the standard output.
At least one of the -1, -k, and -p options
must be specified.
The db_checkpoint utility uses a Berkeley DB environment (as described for the
-h option, the environment variable DB_HOME, or
because the utility was run in a directory containing a Berkeley DB
environment). In order to avoid environment corruption when using a
Berkeley DB environment, db_checkpoint should always be given the chance to
detach from the environment and exit gracefully. To cause db_checkpoint
to release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
The db_checkpoint utility does not attempt to create the Berkeley DB
shared memory regions if they do not already exist. The application
that creates the region should be started first, and once the region is
created, the db_checkpoint utility should be started.
The db_checkpoint utility exits 0 on success, and >0 if an error occurs.
Environment Variables
- DB_HOME
- If the -h option is not specified and the environment variable
DB_HOME is set, it is used as the path of the database home, as described
in DB_ENV->open.
See Also
berkeley_db_svc,
db_archive,
db_checkpoint,
db_deadlock,
db_dump,
db_load,
db_recover,
db_stat,
db_upgrade,
and
db_verify.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
d26 1
a26 1
database log, and periodically calls DB_ENV->txn_checkpoint to checkpoint
a59 3
The DB_ENV->txn_checkpoint function is the underlying function used by the db_checkpoint utility.
See the db_checkpoint utility source code for an example of using DB_ENV->txn_checkpoint
in a IEEE/ANSI Std 1003.1 (POSIX) environment.
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d21 2
a22 2
db_checkpoint [-1Vv] [-h home]
[-k kbytes] [-L file] [-P password] [-p min]
a40 5
-PSpecify an environment password. Although Berkeley DB utilities overwrite
password strings as soon as possible, be aware there may be a window of
vulnerability on systems where unprivileged users can see command-line
arguments or where utilities are not able to overwrite the memory
containing the command-line arguments.
d60 1
a60 1
The DB_ENV->txn_checkpoint method is the underlying interface used by the db_checkpoint utility.
d70 12
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 2
a2 2
d4 1
d22 2
a23 2
db_checkpoint [-1Vv]
[-h home] [-k kbytes] [-L file] [-p min]
d42 5
d66 1
a66 1
The DB_ENV->txn_checkpoint function is the underlying function used by the db_checkpoint utility.
a75 12
See Also
berkeley_db_svc,
db_archive,
db_checkpoint,
db_deadlock,
db_dump,
db_load,
db_recover,
db_stat,
db_upgrade,
and
db_verify.
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d1 2
a2 2
a3 1
d21 2
a22 2
db_checkpoint [-1Vv] [-h home]
[-k kbytes] [-L file] [-P password] [-p min]
a40 5
-PSpecify an environment password. Although Berkeley DB utilities overwrite
password strings as soon as possible, be aware there may be a window of
vulnerability on systems where unprivileged users can see command-line
arguments or where utilities are not able to overwrite the memory
containing the command-line arguments.
d60 1
a60 1
The DB_ENV->txn_checkpoint method is the underlying interface used by the db_checkpoint utility.
d70 12
@