From 831035f6be1d93dbcc9dd121478cff3214599e93 Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Fri, 11 Apr 2008 21:48:35 +0000 Subject: [PATCH] BDB flags link. --- doc/guide/admin/maintenance.sdf | 1 + doc/guide/admin/slapdconf2.sdf | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/guide/admin/maintenance.sdf b/doc/guide/admin/maintenance.sdf index 5c97ac4077..7d480c2ef7 100644 --- a/doc/guide/admin/maintenance.sdf +++ b/doc/guide/admin/maintenance.sdf @@ -90,6 +90,7 @@ recommended: * Log file removal - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/logfile.html}} * Recovery procedures - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/recovery.html}} * Hot failover - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/hotfail.html}} +* Complete list of Berkeley DB flags - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_flags.html}} Advanced installations can use special environment settings to fine-tune some Berkeley DB options (change the log file limit, etc). This can be done by using diff --git a/doc/guide/admin/slapdconf2.sdf b/doc/guide/admin/slapdconf2.sdf index d4c595c4f9..912d4df588 100644 --- a/doc/guide/admin/slapdconf2.sdf +++ b/doc/guide/admin/slapdconf2.sdf @@ -776,7 +776,8 @@ delete transaction log files as soon as their contents have been checkpointed and they are no longer needed. Without this setting the transaction log files will continue to accumulate until some other cleanup procedure removes them. See the Berkeley DB documentation for the -{{EX:db_archive}} command for details. +{{EX:db_archive}} command for details. For a complete list of Berkeley DB +flags please see - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_flags.html}} Ideally the BDB cache must be at least as large as the working set of the database, the log buffer size -- 2.39.5