diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/env_db_config.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/env_db_config.html')
| -rw-r--r-- | docs/programmer_reference/env_db_config.html | 72 |
1 files changed, 37 insertions, 35 deletions
diff --git a/docs/programmer_reference/env_db_config.html b/docs/programmer_reference/env_db_config.html index bd9add35..9f6d7c2f 100644 --- a/docs/programmer_reference/env_db_config.html +++ b/docs/programmer_reference/env_db_config.html @@ -14,17 +14,16 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> - <th colspan="3" align="center">DB_CONFIG configuration file</th> + <th colspan="3" align="center">DB_CONFIG configuration + file</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="env_error.html">Prev</a> </td> - <th width="60%" align="center">Chapter 9. - The Berkeley DB Environment - </th> + <th width="60%" align="center">Chapter 9. The Berkeley DB Environment </th> <td width="20%" align="right"> <a accesskey="n" href="env_naming.html">Next</a></td> </tr> </table> @@ -34,40 +33,43 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="env_db_config"></a>DB_CONFIG configuration file</h2> + <h2 class="title" style="clear: both"><a id="env_db_config"></a>DB_CONFIG configuration + file</h2> </div> </div> </div> <p> - Almost all of the configuration information that can be specified to - <a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> methods can also be specified using a configuration file. - If a file named DB_CONFIG exists in the database home directory, it - will be read for lines of the format - <span class="bold"><strong>NAME VALUE</strong></span>. -</p> - <p> - One or more whitespace characters are used to delimit the two parts of - the line, and trailing whitespace characters are discarded. All empty - lines or lines whose first character is a whitespace or hash - (<span class="bold"><strong>#</strong></span>) character will be ignored. Each - line must specify both the NAME and the VALUE of the pair. The - specific NAME VALUE pairs are documented in the manual for the - corresponding methods (for example, the <a href="../api_reference/C/envset_data_dir.html" class="olink">DB_ENV->set_data_dir()</a> documentation - includes NAME VALUE pair information Berkeley DB administrators can use - to configure locations for database files). -</p> - <p><a id="env_db_config.DB_CONFIG"></a> - The DB_CONFIG configuration file is intended to allow database - environment administrators to customize environments independent of - applications using the environment. For example, a database - administrator can move the database log and data files to a different - location without application recompilation. In addition, because the - DB_CONFIG file is read when the database environment is opened, it can - be used to overrule application configuration done before that time. - For example a database administrator could override the compiled-in - application cache size to a size more appropriate for a specific - machine. -</p> + Almost all of the configuration information that can be + specified to <a href="../api_reference/C/env.html" class="olink">DB_ENV class</a> methods can also be specified using + a configuration file. If a file named DB_CONFIG exists in the + database home directory, it will be read for lines of the + format <span class="bold"><strong>NAME VALUE</strong></span>. + </p> + <p> + One or more whitespace characters are used to delimit the + two parts of the line, and trailing whitespace characters are + discarded. All empty lines or lines whose first character is a + whitespace or hash (<span class="bold"><strong>#</strong></span>) + character will be ignored. Each line must specify both the + NAME and the VALUE of the pair. The specific NAME VALUE pairs + are documented in the manual for the corresponding methods + (for example, the <a href="../api_reference/C/envadd_data_dir.html" class="olink">DB_ENV->add_data_dir()</a> documentation includes + NAME VALUE pair information Berkeley DB administrators can use + to configure locations for database files). + </p> + <p><a id="env_db_config.DB_CONFIG"></a> + The DB_CONFIG configuration + file is intended to allow database environment administrators + to customize environments independent of applications using + the environment. For example, a database administrator can + move the database log and data files to a different location + without application recompilation. In addition, because the + DB_CONFIG file is read when the database environment is + opened, it can be used to overrule application configuration + done before that time. For example a database administrator + could override the compiled-in application cache size to a + size more appropriate for a specific machine. + </p> </div> <div class="navfooter"> <hr /> |