From e523c3b1f2ab90f2b424bdefe674a0fd3d8da7f4 Mon Sep 17 00:00:00 2001 From: Ludovic Poitou <ludovic.poitou@forgerock.com> Date: Thu, 23 Jun 2011 17:07:56 +0000 Subject: [PATCH] Fix for issue OPENDJ-214. Rebranded as OpenDJ and now uses product-name variable. --- opends/src/admin/messages/LocalDBBackendCfgDefn.properties | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties index 82052a9..a8e6b78 100644 --- a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties +++ b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties @@ -21,7 +21,7 @@ property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files. property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact. property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend. -property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents. +property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDJ directory server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents. property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files. property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files. property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory). @@ -49,9 +49,9 @@ property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled. property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file. property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk. -property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server). +property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDJ directory server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server). property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk. -property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally). +property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDJ directory server or the JVM exits abnormally). property.disk-full-threshold.synopsis=Full disk threshold to limit database updates property.disk-full-threshold.description=When the available free space on the disk used by this database instance falls below the value specified, no updates are permitted and the server returns an UNWILLING_TO_PERFORM error. Updates are allowed again as soon as free space rises above the threshold. property.disk-low-threshold.synopsis=Low disk threshold to limit database updates @@ -61,19 +61,19 @@ property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database. property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry. property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data. -property.import-queue-size.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDS 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. -property.import-queue-size.requires-admin-action.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDS 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. -property.import-thread-count.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDS 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. -property.import-thread-count.description=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDS 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. +property.import-queue-size.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDJ 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. +property.import-queue-size.requires-admin-action.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDJ 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. +property.import-thread-count.synopsis=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDJ 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. +property.import-thread-count.description=This parameter has been deprecated in OpenDS 2.1 and will be removed in OpenDJ 3.0. It is only being kept for migration ease and is ignored in OpenDS versions after 2.0. property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress. property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained. property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit. property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit. -property.index-filter-analyzer-enabled.synopsis=Indicates whether to gather statistical information about the search filters processed by the Directory Server while evaluating the usage of indexes. +property.index-filter-analyzer-enabled.synopsis=Indicates whether to gather statistical information about the search filters processed by the directory server while evaluating the usage of indexes. property.index-filter-analyzer-enabled.description=Analyzing indexes requires gathering search filter usage patterns from user requests, especially for values as specified in the filters and subsequently looking the status of those values into the index files. When a search requests is processed, internal or user generated, a first phase uses indexes to find potential entries to be returned. Depending on the search filter, if the index of one of the specified attributes matches too many entries (exceeds the index entry limit), the search becomes non-indexed. In any case, all entries thus gathered (or the entire DIT) are matched against the filter for actually returning the search result. property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation. property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend. -property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution. +property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDJ documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution. property.max-entries.synopsis=The maximum number of search filter statistics to keep. property.max-entries.description=When the maximum number of search filter is reached, the least used one will be deleted. property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized. -- Gitblit v1.10.0