NNAAMMEE db_checkpoint - the DB database checkpoint utility SSYYNNOOPPSSIISS ddbb__cchheecckkppooiinntt [--11vv] [--hh hhoommee] [--kk kkbbyytteess] [--LL ffiillee] [--pp mmiinn] DDEESSCCRRIIPPTTIIOONN The _d_b___c_h_e_c_k_p_o_i_n_t utility is a daemon process that moni- tors the database log and periodically calls _t_x_n___c_h_e_c_k_- _p_o_i_n_t(3) to checkpoint it. The options are as follows: --11 Checkpoint the log once, and then exit. --hh Specify a home directory for the database. --kk Checkpoint the database at least as often as every _k_b_y_t_e_s of log file are written. --LL 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 util- ity starting running. db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995 This file will be removed if the db_checkpoint util- ity exits gracefully. --pp Checkpoint the database at least every _m_i_n minutes. --vv Write the time of each checkpoint to the standard output. At least one of the --11, --kk and --pp options must be speci- fied. The _d_b___c_h_e_c_k_p_o_i_n_t utility attaches to DB shared memory regions. In order to avoid region corruption, it should always be given the chance to detach and exit gracefully. To cause _d_b___c_h_e_c_k_p_o_i_n_t to clean up after itself and exit, send it an interrupt signal (SIGINT). The _d_b___c_h_e_c_k_p_o_i_n_t utility exits 0 on success, and >0 if an error occurs. EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS The following environment variables affect the execution of _d_b___c_h_e_c_k_p_o_i_n_t: DB_HOME If the --hh option is not specified and the environment variable _D_B___H_O_M_E is set, it is used as the path of the database home, as described in _d_b___a_p_p_i_n_i_t(3). SSEEEE AALLSSOO The DB library is a family of groups of functions that provides a modular programming interface to transactions and record-oriented file access. The library includes support for transactions, locking, logging and file page caching, as well as various indexed access methods. Many of the functional groups (e.g., the file page caching functions) are useful independent of the other DB func- tions, although some functional groups are explicitly based on other functional groups (e.g., transactions and logging). For a general description of the DB package, see _d_b___i_n_t_r_o(3). _d_b___a_r_c_h_i_v_e(1), _d_b___c_h_e_c_k_p_o_i_n_t(1), _d_b___d_e_a_d_l_o_c_k(1), _d_b___d_u_m_p(1), _d_b___l_o_a_d(1), _d_b___r_e_c_o_v_e_r(1), _d_b___s_t_a_t(1), _d_b___i_n_t_r_o(3), _d_b___a_p_p_i_n_i_t(3), _d_b___c_u_r_s_o_r(3), _d_b___d_b_m(3), _d_b___i_n_t_e_r_n_a_l(3), _d_b___l_o_c_k(3), _d_b___l_o_g(3), _d_b___m_p_o_o_l(3), _d_b___o_p_e_n(3), _d_b___t_h_r_e_a_d(3), _d_b___t_x_n(3)