From 158c7947c36f747134375220d0f0bdeba5407134 Mon Sep 17 00:00:00 2001
From: abobrov <abobrov@localhost>
Date: Sat, 08 Dec 2007 18:01:08 +0000
Subject: [PATCH] - Fix description and reflect the real cache percent upper limit as imposed by JE.
---
opends/src/admin/defn/org/opends/server/admin/std/FileSystemEntryCacheConfiguration.xml | 40 ++++++++++++++++++++--------------------
1 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/FileSystemEntryCacheConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/FileSystemEntryCacheConfiguration.xml
index b9c5c1c..89ca4e1 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/FileSystemEntryCacheConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/FileSystemEntryCacheConfiguration.xml
@@ -41,25 +41,25 @@
based file system, although any file system will do for this cache
to function. Entries are maintained either by FIFO (default) or LRU
(configurable) based list implementation. Cache sizing is based on
- the size or percentage of free space available in the file system,
- such that if enough memory is free, then adding an entry to the
- cache will not require purging, but if more than a specified
- percentage of the file system available space is already consumed,
- then one or more entries will need to be removed in order to make
- room for a new entry. It is also possible to configure a maximum
- number of entries for the cache. If this is specified, then the
- number of entries will not be allowed to exceed this value, but it
- may not be possible to hold this many entries if the available
- memory fills up first. Other configurable parameters for this cache
- include the maximum length of time to block while waiting to acquire
- a lock, and a set of filters that may be used to define criteria for
- determining which entries are stored in the cache. If a set of
- filters are provided then an entry must match at least one of them
- in order to be stored in the cache. JE environment cache size can
- also be configured either as percentage of the free memory available
- in the JVM, or as an absolute size in bytes. This cache has a
- persistence property which, if enabled, allows for the contents of
- the cache to persist across server or cache restarts.
+ the size of free space available in the file system, such that if
+ enough memory is free, then adding an entry to the cache will not
+ require purging, but if more than a specified size of the file
+ system available space is already consumed, then one or more entries
+ will need to be removed in order to make room for a new entry. It is
+ also possible to configure a maximum number of entries for the cache.
+ If this is specified, then the number of entries will not be allowed
+ to exceed this value, but it may not be possible to hold this many
+ entries if the available memory fills up first. Other configurable
+ parameters for this cache include the maximum length of time to block
+ while waiting to acquire a lock, and a set of filters that may be
+ used to define criteria for determining which entries are stored in
+ the cache. If a set of filters are provided then an entry must match
+ at least one of them in order to be stored in the cache.
+ JE environment cache size can also be configured either as percentage
+ of the free memory available in the JVM, or as an absolute size in
+ bytes. This cache has a persistence property which, if enabled,
+ allows for the contents of the cache to persist across server or
+ cache restarts.
</adm:description>
<adm:profile name="ldap">
<ldap:object-class>
@@ -235,7 +235,7 @@
</adm:defined>
</adm:default-behavior>
<adm:syntax>
- <adm:integer lower-limit="0" upper-limit="100" />
+ <adm:integer lower-limit="0" upper-limit="90" />
</adm:syntax>
<adm:profile name="ldap">
<ldap:attribute>
--
Gitblit v1.10.0