Penguin
Recent Changes
Blame: db_checkpoint(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of db_checkpoint(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 DB_CHECKPOINT
2 !!!DB_CHECKPOINT
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 ENVIRONMENT VARIABLES
7 SEE ALSO
8 ----
9 !!NAME
10
11
12 db_checkpoint - the DB database checkpoint utility
13 !!SYNOPSIS
14
15
16 __db_checkpoint__ [[__-1v__] [[__-h home__] [[__-k kbytes__] [[__-L file__] [[__-p min__]
17 !!DESCRIPTION
18
19
20 The ''db_checkpoint'' utility is a daemon process that
21 monitors the database log and periodically calls
22 ''txn_checkpoint''(3) to checkpoint it.
23
24
25 The options are as follows:
26
27
28 __-1__
29
30
31 Checkpoint the log once, and then exit.
32
33
34 __-h__
35
36
37 Specify a home directory for the database.
38
39
40 __-k__
41
42
43 Checkpoint the database at least as often as every
44 ''kbytes'' of log file are written.
45
46
47 __-L__
48
49
50 Log the execution of the db_checkpoint utility to the
51 specified file in the following format, where ``###'' is the
52 process ID, and the date is the time the utility starting
53 running.
54
55
56 db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
57
58
59 This file will be removed if the db_checkpoint utility exits
60 gracefully.
61
62
63 __-p__
64
65
66 Checkpoint the database at least every ''min''
67 minutes.
68
69
70 __-v__
71
72
73 Write the time of each checkpoint to the standard
74 output.
75
76
77 At least one of the __-1__, __-k__ and __-p__
78 options must be specified.
79
80
81 The ''db_checkpoint'' utility attaches to DB shared
82 memory regions. In order to avoid region corruption, it
83 should always be given the chance to detach and exit
84 gracefully. To cause ''db_checkpoint'' to clean up after
85 itself and exit, send it an interrupt signal
86 (SIGINT).
87
88
89 The ''db_checkpoint'' utility exits 0 on success, and
90 ''
91 !!ENVIRONMENT VARIABLES
92
93
94 The following environment variables affect the execution of
95 ''db_checkpoint'':
96
97
98 DB_HOME
99
100
101 If the __-h__ option is not specified and the environment
102 variable ''DB_HOME'' is set, it is used as the path of
103 the database home, as described in
104 ''db_appinit''(3).
105 !!SEE ALSO
106
107
108 The DB library is a family of groups of functions that
109 provides a modular programming interface to transactions and
110 record-oriented file access. The library includes support
111 for transactions, locking, logging and file page caching, as
112 well as various indexed access methods. Many of the
113 functional groups (e.g., the file page caching functions)
114 are useful independent of the other DB functions, although
115 some functional groups are explicitly based on other
116 functional groups (e.g., transactions and
117 logging).
118
119
120 ''db_archive''(1), ''db_checkpoint''(1),
121 ''db_deadlock''(1), ''db_dump''(1), ''db_load''(1),
122 ''db_recover''(1), ''db_stat''(1),
123 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.