{ "content": [ { "type": "text", "text": "# DB5.3_CHECKPOINT(1) (man)\n\n**Summary:** db5.3checkpoint - Periodically checkpoint transactions\n\n**Synopsis:** db5.3checkpoint [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| -1 | — | — | the last checkpoint and then exit. |\n| -h | — | — | directory is used. |\n| -k | — | — | |\n| -L | — | — | ing format, where ### is the process ID, and the date is the time the utility was started. dbcheckpoint: ### Wed Jun 15 |\n| -P | — | — | strings as soon as possible, be aware there may be a window of vulnerability on sys‐ tems where unprivileged users can s |\n| -p | — | — | since the last checkpoint. |\n| -V | — | — | |\n| -v | — | — | At least one of the -1, -k, and -p options must be specified. The db5.3checkpoint utility uses a Berkeley DB environment |\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (2 lines)\n- **DESCRIPTION** (3 lines)\n- **OPTIONS** (1 lines) — 8 subsections\n - -1 (2 lines)\n - -h (2 lines)\n - -k (1 lines)\n - -L (8 lines)\n - -P (4 lines)\n - -p (2 lines)\n - -V (1 lines)\n - -v (19 lines)\n- **ENVIRONMENT** (4 lines)\n- **AUTHORS** (7 lines)\n\n## Full Content\n\n### NAME\n\ndb5.3checkpoint - Periodically checkpoint transactions\n\n### SYNOPSIS\n\ndb5.3checkpoint [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]\n\n### DESCRIPTION\n\nThe db5.3checkpoint utility is a daemon process that monitors the database log, and periodi‐\ncally calls DBENV->txncheckpoint to checkpoint it.\n\n### OPTIONS\n\n#### -1\n\nthe last checkpoint and then exit.\n\n#### -h\n\ndirectory is used.\n\n#### -k\n\n#### -L\n\ning format, where ### is the process ID, and the date is the time the utility was\nstarted.\n\n\ndbcheckpoint: ### Wed Jun 15 01:23:45 EDT 1995\n\nThis file will be removed if the db5.3checkpoint utility exits gracefully.\n\n#### -P\n\nstrings as soon as possible, be aware there may be a window of vulnerability on sys‐\ntems where unprivileged users can see command-line arguments or where utilities are\nnot able to overwrite the memory containing the command-line arguments.\n\n#### -p\n\nsince the last checkpoint.\n\n#### -V\n\n#### -v\n\nAt least one of the -1, -k, and -p options must be specified.\n\nThe db5.3checkpoint utility uses a Berkeley DB environment (as described for the -h option,\nthe environment variable DBHOME, or because the utility was run in a directory containing a\nBerkeley DB environment). In order to avoid environment corruption when using a Berkeley DB\nenvironment, db5.3checkpoint should always be given the chance to detach from the environ‐\nment and exit gracefully. To cause db5.3checkpoint to release all environment resources and\nexit cleanly, send it an interrupt signal (SIGINT).\n\nThe db5.3checkpoint utility does not attempt to create the Berkeley DB shared memory regions\nif they do not already exist. The application that creates the region should be started\nfirst, and once the region is created, the db5.3checkpoint utility should be started.\n\nThe DBENV->txncheckpoint method is the underlying method used by the db5.3checkpoint util‐\nity. See the dbcheckpoint utility source code for an example of using DBENV->txncheckpoint\nin a IEEE/ANSI Std 1003.1 (POSIX) environment.\n\nThe db5.3checkpoint utility exits 0 on success, and >0 if an error occurs.\n\n### ENVIRONMENT\n\nDBHOME\nIf the -h option is not specified and the environment variable DBHOME is set, it is\nused as the path of the database home, as described in DBENV->open.\n\n### AUTHORS\n\nSleepycat Software, Inc. This manual page was created based on the HTML documentation for\ndbcheckpoint from Sleepycat, by Thijs Kinkhorst , for the Debian system\n(but may be used by others).\n\n\n\n28 January 2005 DB5.3CHECKPOINT(1)\n\n" } ], "structuredContent": { "command": "DB5.3_CHECKPOINT", "section": "1", "mode": "man", "summary": "db5.3checkpoint - Periodically checkpoint transactions", "synopsis": "db5.3checkpoint [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]", "flags": [ { "flag": "-1", "long": null, "arg": null, "description": "the last checkpoint and then exit." }, { "flag": "-h", "long": null, "arg": null, "description": "directory is used." }, { "flag": "-k", "long": null, "arg": null, "description": "" }, { "flag": "-L", "long": null, "arg": null, "description": "ing format, where ### is the process ID, and the date is the time the utility was started. dbcheckpoint: ### Wed Jun 15 01:23:45 EDT 1995 This file will be removed if the db5.3checkpoint utility exits gracefully." }, { "flag": "-P", "long": null, "arg": null, "description": "strings as soon as possible, be aware there may be a window of vulnerability on sys‐ tems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments." }, { "flag": "-p", "long": null, "arg": null, "description": "since the last checkpoint." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-v", "long": null, "arg": null, "description": "At least one of the -1, -k, and -p options must be specified. The db5.3checkpoint utility uses a Berkeley DB environment (as described for the -h option, the environment variable DBHOME, 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, db5.3checkpoint should always be given the chance to detach from the environ‐ ment and exit gracefully. To cause db5.3checkpoint to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). The db5.3checkpoint 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 db5.3checkpoint utility should be started. The DBENV->txncheckpoint method is the underlying method used by the db5.3checkpoint util‐ ity. See the dbcheckpoint utility source code for an example of using DBENV->txncheckpoint in a IEEE/ANSI Std 1003.1 (POSIX) environment. The db5.3checkpoint utility exits 0 on success, and >0 if an error occurs." } ], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 3, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-1", "lines": 2, "flag": "-1" }, { "name": "-h", "lines": 2, "flag": "-h" }, { "name": "-k", "lines": 1, "flag": "-k" }, { "name": "-L", "lines": 8, "flag": "-L" }, { "name": "-P", "lines": 4, "flag": "-P" }, { "name": "-p", "lines": 2, "flag": "-p" }, { "name": "-V", "lines": 1, "flag": "-V" }, { "name": "-v", "lines": 19, "flag": "-v" } ] }, { "name": "ENVIRONMENT", "lines": 4, "subsections": [] }, { "name": "AUTHORS", "lines": 7, "subsections": [] } ] } }