From 50c662df0991513185cc2c079a4283ddd669b3dc Mon Sep 17 00:00:00 2001 From: jpikus <jpikus@localhost> Date: Mon, 14 Sep 2009 15:37:06 +0000 Subject: [PATCH] update l10n generated files --- opends/src/admin/messages/LocalDBBackendCfgDefn.properties | 14 ++++++++------ 1 files changed, 8 insertions(+), 6 deletions(-) diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties index 2075bdf..026a78b 100644 --- a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties +++ b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties @@ -26,7 +26,7 @@ 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). property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first). -property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached. +property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf nodes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached. property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information. property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread. property.db-log-file-max.synopsis=Specifies the maximum size for a database log file. @@ -36,8 +36,10 @@ property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL. property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization. property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization. +property.db-num-cleaner-threads.default-behavior.alias.synopsis=Let the server decide. property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database. property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server. +property.db-num-lock-tables.default-behavior.alias.synopsis=Let the server decide. 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. @@ -49,10 +51,10 @@ 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=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import. -property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress. -property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import. -property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system. +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-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. @@ -64,7 +66,7 @@ property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load. property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations. property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail. -property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled). +property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability-mode property is also enabled). property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations. relation.local-db-index.user-friendly-name=Local DB Index relation.local-db-index.user-friendly-plural-name=Local DB Indexes -- Gitblit v1.10.0