# CDDL HEADER START
|
#
|
# The contents of this file are subject to the terms of the
|
# Common Development and Distribution License, Version 1.0 only
|
# (the "License"). You may not use this file except in compliance
|
# with the License.
|
#
|
# You can obtain a copy of the license at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE
|
# or https://OpenDS.dev.java.net/OpenDS.LICENSE.
|
# See the License for the specific language governing permissions
|
# and limitations under the License.
|
#
|
# When distributing Covered Code, include this CDDL HEADER in each
|
# file and include the License file at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE. If applicable,
|
# add the following below this CDDL HEADER, with the fields enclosed
|
# by brackets "[]" replaced with your own identifying information:
|
# Portions Copyright [yyyy] [name of copyright owner]
|
#
|
# CDDL HEADER END
|
#
|
# Copyright 2006-2009 Sun Microsystems, Inc.
|
#
|
# Global directives
|
#
|
global.category=CONFIG
|
#
|
# Format string definitions
|
#
|
# Keys must be formatted as follows:
|
#
|
# [SEVERITY]_[DESCRIPTION]_[ORDINAL]
|
#
|
# where:
|
#
|
# SEVERITY is one of:
|
# [INFO, MILD_WARN, SEVERE_WARN, MILD_ERR, SEVERE_ERR, FATAL_ERR, DEBUG, NOTICE]
|
#
|
# DESCRIPTION is an upper case string providing a hint as to the context of
|
# the message in upper case with the underscore ('_') character serving as
|
# word separator
|
#
|
# ORDINAL is an integer unique among other ordinals in this file
|
#
|
MILD_ERR_CONFIG_ATTR_IS_REQUIRED_1=\u914d\u7f6e\u5c5e\u6027 %s \u81f3\u5c11\u9700\u8981\u5177\u6709\u4e00\u4e2a\u503c\uff0c\u4f46\u5bfc\u81f4\u7684\u64cd\u4f5c\u5c06\u4f1a\u5220\u9664\u6240\u6709\u503c
|
MILD_ERR_CONFIG_ATTR_REJECTED_VALUE_2=\u4e3a\u914d\u7f6e\u5c5e\u6027 %2$s \u63d0\u4f9b\u7684\u503c %1$s \u88ab\u62d2\u7edd\u3002\u63d0\u4f9b\u7684\u539f\u56e0\u4e3a: %s
|
MILD_ERR_CONFIG_ATTR_SET_VALUES_IS_SINGLE_VALUED_3=\u914d\u7f6e\u5c5e\u6027 %s \u662f\u5355\u503c\u5c5e\u6027\uff0c\u4f46\u63d0\u4f9b\u4e86\u591a\u4e2a\u503c
|
MILD_ERR_CONFIG_ATTR_ADD_VALUES_IS_SINGLE_VALUED_4=\u914d\u7f6e\u5c5e\u6027 %s \u662f\u5355\u503c\u5c5e\u6027\uff0c\u4f46\u6dfb\u52a0\u63d0\u4f9b\u7684\u503c\u5c06\u4f7f\u5176\u5177\u6709\u591a\u4e2a\u503c
|
MILD_ERR_CONFIG_ATTR_ADD_VALUES_ALREADY_EXISTS_5=\u914d\u7f6e\u5c5e\u6027 %s \u5df2\u5305\u542b\u503c %s
|
MILD_ERR_CONFIG_ATTR_NO_SUCH_VALUE_6=\u65e0\u6cd5\u4ece\u914d\u7f6e\u5c5e\u6027 %2$s \u4e2d\u5220\u9664\u503c %1$s\uff0c\u56e0\u4e3a\u6307\u5b9a\u7684\u503c\u4e0d\u5b58\u5728
|
MILD_ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUE_7=\u65e0\u6cd5\u8bbe\u7f6e\u5e03\u5c14\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\uff0c\u56e0\u4e3a\u63d0\u4f9b\u7684\u503c %s \u4e0d\u662f\u201c\u771f\u201d\u6216\u201c\u5047\u201d
|
MILD_ERR_CONFIG_ATTR_NO_INT_VALUE_8=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u4f5c\u4e3a\u6574\u6570\u8fdb\u884c\u68c0\u7d22\uff0c\u56e0\u4e3a\u8be5\u5c5e\u6027\u6ca1\u6709\u4efb\u4f55\u503c
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_INT_VALUES_9=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u4f5c\u4e3a\u6574\u6570\u8fdb\u884c\u68c0\u7d22\uff0c\u56e0\u4e3a\u8be5\u5c5e\u6027\u5177\u6709\u591a\u4e2a\u503c
|
MILD_ERR_CONFIG_ATTR_VALUE_OUT_OF_INT_RANGE_10=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u4f5c\u4e3a Java int \u8fdb\u884c\u68c0\u7d22\uff0c\u56e0\u4e3a\u8be5\u503c\u4e0d\u5728 int \u5141\u8bb8\u7684\u8303\u56f4\u5185
|
MILD_ERR_CONFIG_ATTR_INVALID_INT_VALUE_11=\u65e0\u6cd5\u8bbe\u7f6e\u6574\u6570\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\uff0c\u56e0\u4e3a\u65e0\u6cd5\u5c06\u63d0\u4f9b\u7684\u503c %s \u89e3\u91ca\u4e3a\u6574\u6570\u503c: %s
|
MILD_ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUND_12=\u65e0\u6cd5\u8bbe\u7f6e\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\uff0c\u56e0\u4e3a\u63d0\u4f9b\u7684\u503c %d \u5c0f\u4e8e\u5141\u8bb8\u7684\u6700\u5c0f\u503c %d
|
MILD_ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUND_13=\u65e0\u6cd5\u8bbe\u7f6e\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\uff0c\u56e0\u4e3a\u63d0\u4f9b\u7684\u503c %d \u5927\u4e8e\u5141\u8bb8\u7684\u6700\u5927\u503c %d
|
MILD_ERR_CONFIG_ATTR_INT_COULD_NOT_PARSE_14=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a\u6574\u6570\u503c: %3$s
|
MILD_ERR_CONFIG_ATTR_NO_STRING_VALUE_15=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u4f5c\u4e3a\u5b57\u7b26\u4e32\u8fdb\u884c\u68c0\u7d22\uff0c\u56e0\u4e3a\u8be5\u5c5e\u6027\u6ca1\u6709\u4efb\u4f55\u503c
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_STRING_VALUES_16=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u4f5c\u4e3a\u5b57\u7b26\u4e32\u8fdb\u884c\u68c0\u7d22\uff0c\u56e0\u4e3a\u8be5\u5c5e\u6027\u5177\u6709\u591a\u4e2a\u503c
|
MILD_ERR_CONFIG_ATTR_EMPTY_STRING_VALUE_17=\u4e3a\u914d\u7f6e\u5c5e\u6027 %s \u63d0\u4f9b\u4e86\u7a7a\u503c\u5b57\u7b26\u4e32
|
MILD_ERR_CONFIG_ATTR_VALUE_NOT_ALLOWED_18=\u503c %s \u672a\u5305\u542b\u5728\u914d\u7f6e\u5c5e\u6027 %s \u7684\u53ef\u63a5\u53d7\u503c\u5217\u8868\u4e2d
|
MILD_ERR_CONFIG_ATTR_INVALID_UNIT_19='%s' \u4e0d\u662f\u914d\u7f6e\u5c5e\u6027 %s \u7684\u6709\u6548\u5355\u4f4d
|
MILD_ERR_CONFIG_ATTR_NO_UNIT_DELIMITER_20=\u65e0\u6cd5\u5c06 %s \u89e3\u7801\u4e3a\u6574\u6570\u503c\u548c\u914d\u7f6e\u5c5e\u6027 %s \u7684\u5355\u4f4d\uff0c\u56e0\u4e3a\u627e\u4e0d\u5230\u4efb\u4f55\u503c/\u5355\u4f4d\u5206\u9694\u7b26
|
MILD_ERR_CONFIG_ATTR_COULD_NOT_PARSE_INT_COMPONENT_21=\u65e0\u6cd5\u89e3\u7801\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u7684\u6574\u6570\u90e8\u5206: %3$s
|
MILD_ERR_CONFIG_ATTR_INVALID_VALUE_WITH_UNIT_22=\u4e0d\u5141\u8bb8\u4f7f\u7528\u4e3a\u5177\u6709\u5355\u4f4d\u5c5e\u6027 %2$s \u7684\u6574\u6570\u63d0\u4f9b\u7684\u503c %1$s: %3$s
|
MILD_ERR_CONFIG_ENTRY_CONFLICTING_CHILD_23=\u65e0\u6cd5\u5c06\u914d\u7f6e\u6761\u76ee %s \u4f5c\u4e3a\u914d\u7f6e\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u8fdb\u884c\u6dfb\u52a0\uff0c\u56e0\u4e3a\u5df2\u53d1\u73b0\u5177\u6709\u8be5 DN \u7684\u5b50\u6761\u76ee
|
MILD_ERR_CONFIG_ENTRY_NO_SUCH_CHILD_24=\u65e0\u6cd5\u5c06\u6761\u76ee %s \u4f5c\u4e3a\u914d\u7f6e\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u8fdb\u884c\u5220\u9664\uff0c\u56e0\u4e3a\u8be5\u6761\u76ee\u4e0d\u5305\u542b\u5177\u6709\u6307\u5b9a DN \u7684\u5b50\u6761\u76ee
|
MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_NONLEAF_25=\u65e0\u6cd5\u5c06\u6761\u76ee %s \u4f5c\u4e3a\u914d\u7f6e\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u8fdb\u884c\u5220\u9664\uff0c\u56e0\u4e3a\u8be5\u6761\u76ee\u5177\u6709\u81ea\u5df1\u7684\u5b50\u6761\u76ee\uff08\u4e0d\u53ef\u4ee5\u5220\u9664\u975e\u53f6\u6761\u76ee\uff09
|
###FATAL_ERR_CONFIG_FILE_DOES_NOT_EXIST_26=The specified configuration file %s \
|
### does not exist or is not readable
|
###FATAL_ERR_CONFIG_FILE_CANNOT_VERIFY_EXISTENCE_27=An unexpected error occurred \
|
### while attempting to determine whether configuration file %s exists: %s
|
###FATAL_ERR_CONFIG_FILE_CANNOT_OPEN_FOR_READ_28=An error occurred while \
|
### attempting to open the configuration file %s for reading: %s
|
###FATAL_ERR_CONFIG_FILE_READ_ERROR_29=An error occurred while attempting to \
|
### read the contents of configuration file %s: %s
|
MILD_ERR_CONFIG_ATTR_OPTIONS_NOT_ALLOWED_30=\u68c0\u6d4b\u5230\u65e0\u6548\u7684\u914d\u7f6e\u5c5e\u6027 %s\uff1a\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5141\u8bb8\u4f7f\u7528\u7684\u552f\u4e00\u5c5e\u6027\u9009\u9879\u4e3a "pending"\uff0c\u5b83\u6307\u793a\u4e00\u7ec4\u5f85\u5904\u7406\u7684\u503c
|
###FATAL_ERR_CONFIG_FILE_INVALID_LDIF_ENTRY_31=An error occurred at or near line \
|
### %d while trying to parse the configuration from LDIF file %s: %s
|
###FATAL_ERR_CONFIG_FILE_EMPTY_32=The specified configuration file %s does not \
|
### appear to contain any configuration entries
|
###FATAL_ERR_CONFIG_FILE_INVALID_BASE_DN_33=The first entry read from LDIF \
|
### configuration file %s had a DN of "%s" rather than the expected "%s" which \
|
### should be used as the Directory Server configuration root
|
###FATAL_ERR_CONFIG_FILE_GENERIC_ERROR_34=An unexpected error occurred while \
|
### attempting to process the Directory Server configuration file %s: %s
|
###FATAL_ERR_CONFIG_FILE_DUPLICATE_ENTRY_35=Configuration entry %s starting at \
|
### or near line %s in the LDIF configuration file %s has the same DN as another \
|
### entry already read from that file
|
###FATAL_ERR_CONFIG_FILE_NO_PARENT_36=Configuration entry %s starting at or near \
|
### line %d in the configuration LDIF file %s does not appear to have a parent \
|
### entry (expected parent DN was %s)
|
###FATAL_ERR_CONFIG_FILE_UNKNOWN_PARENT_37=The Directory Server was unable to \
|
### determine the parent DN for configuration entry %s starting at or near line \
|
### %d in the configuration LDIF file %s
|
###FATAL_ERR_CONFIG_CANNOT_DETERMINE_SERVER_ROOT_38=Unable to determine the \
|
### Directory Server instance root from either an environment variable or based \
|
### on the location of the configuration file. Please set an environment \
|
### variable named %s with a value containing the absolute path to the server \
|
### installation root
|
###SEVERE_ERR_CONFIG_FILE_WRITE_ERROR_39=An unexpected error occurred while \
|
### trying to write configuration entry %s to LDIF: %s
|
###SEVERE_ERR_CONFIG_FILE_CLOSE_ERROR_40=An unexpected error occurred while \
|
### trying to close the LDIF writer: %s
|
###SEVERE_ERR_CONFIG_FILE_UNWILLING_TO_IMPORT_41=The Directory Server \
|
### configuration may not be altered by importing a new configuration from LDIF
|
###FATAL_ERR_CONFIG_LOGGER_CANNOT_GET_BASE_42=An error occurred while attempting \
|
### to retrieve the base logger entry cn=Loggers,cn=config from the Directory \
|
### Server configuration: %s
|
###SEVERE_WARN_CONFIG_LOGGER_BASE_DOES_NOT_EXIST_43=The logger configuration \
|
### base cn=Loggers,cn=config does not exist in the Directory Server \
|
### configuration. Logging facilities will not be available until this entry is \
|
### created and the Directory Server is restarted
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ACCESS_LOGGERS_44=There are no active \
|
### access loggers defined in the Directory Server configuration. No access \
|
### logging will be performed
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ERROR_LOGGERS_45=There are no active \
|
### error loggers defined in the Directory Server configuration. No error \
|
### logging will be performed
|
MILD_WARN_CONFIG_LOGGER_NO_ACTIVE_DEBUG_LOGGERS_46=\u672a\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5b9a\u4e49\u4efb\u4f55\u6d3b\u52a8\u8c03\u8bd5\u8bb0\u5f55\u5668\u3002\u4e0d\u4f1a\u6267\u884c\u4efb\u4f55\u8c03\u8bd5\u65e5\u5fd7\u8bb0\u5f55
|
###SEVERE_ERR_CONFIG_LOGGER_ENTRY_UNACCEPTABLE_47=Configuration entry %s does \
|
### not contain a valid logger configuration: %s. It will be ignored
|
INFO_CONFIG_UNKNOWN_UNACCEPTABLE_REASON_48=\u65e0\u6cd5\u63a5\u53d7\u7684\u672a\u77e5\u539f\u56e0
|
###SEVERE_ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGER_49=An error occurred while \
|
### attempting to create a Directory Server logger from the information in \
|
### configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_OBJECTCLASS_50=Configuration entry %s does \
|
### not contain a valid objectclass for a Directory Server access, error, or \
|
### debug logger definition
|
INFO_CONFIG_LOGGER_DESCRIPTION_CLASS_NAME_51=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u8bb0\u5f55\u5668\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u8bb0\u5f55\u5668\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u8bb0\u5f55\u5668\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_LOGGER_NO_CLASS_NAME_52=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-java-class which \
|
### specifies the fully-qualified class name for the associated logger
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_CLASS_NAME_53=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASS_54=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server access logger: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASS_55=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server error logger: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASS_56=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server debug logger: %s
|
INFO_CONFIG_LOGGER_DESCRIPTION_ENABLED_57=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u8bb0\u5f55\u5668\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_LOGGER_NO_ENABLED_ATTR_58=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-enabled which \
|
### indicates whether the logger should be enabled for use in the Directory \
|
### Server
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ENABLED_VALUE_59=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_CORE_DESCRIPTION_ALLOW_ATTR_EXCEPTIONS_60=\u6307\u793a\u5c5e\u6027\u540d\u79f0\u4e2d\u4f7f\u7528\u7684\u5b57\u7b26\u662f\u5426\u53ef\u4ee5\u5177\u6709\u4e00\u5b9a\u7684\u7075\u6d3b\u6027\u3002\u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0c\u5c5e\u6027\u540d\u79f0\u53ea\u80fd\u5305\u542b ASCII \u5b57\u6bcd\u3001\u6570\u5b57\u548c\u77ed\u5212\u7ebf\uff0c\u5e76\u4e14\u5fc5\u987b\u4ee5\u5b57\u6bcd\u5f00\u5934\u3002\u5982\u679c\u542f\u7528\u4e86\u5c5e\u6027\u540d\u79f0\u4f8b\u5916\u8bbe\u7f6e\uff0c\u5219\u8fd8\u5141\u8bb8\u4f7f\u7528\u4e0b\u5212\u7ebf\u5b57\u7b26\uff0c\u5e76\u4e14\u5c5e\u6027\u540d\u79f0\u8fd8\u53ef\u4ee5\u6570\u5b57\u5f00\u5934\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ALLOW_EXCEPTIONS_61=Configuration entry %s has \
|
### an invalid value for configuration attribute \
|
### ds-cfg-allow-attribute-name-exceptions (it should be a Boolean value of true \
|
### or false): %s
|
INFO_CONFIG_CORE_DESCRIPTION_INVALID_SYNTAX_BEHAVIOR_62=\u76ee\u5f55\u670d\u52a1\u5668\u53d1\u73b0\u67d0\u4e2a\u5c5e\u6027\u7684\u503c\u4e0d\u7b26\u5408\u8be5\u5c5e\u6027\u7684\u8bed\u6cd5\u65f6\u6240\u5c55\u73b0\u7684\u884c\u4e3a\u3002\u5bf9\u4e8e\u8be5\u5c5e\u6027\uff0c\u53ef\u63a5\u53d7\u7684\u503c\u4e3a "reject"\uff08\u62d2\u7edd\u65e0\u6548\u503c\uff09\u3001"warn"\uff08\u63a5\u53d7\u65e0\u6548\u503c\uff0c\u4f46\u8bb0\u5f55\u4e00\u6761\u8b66\u544a\u6d88\u606f\uff09\u6216 "accept"\uff08\u63a5\u53d7\u65e0\u6548\u503c\uff0c\u5e76\u4e14\u4e0d\u53d1\u51fa\u8b66\u544a\uff09\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ENFORCE_STRICT_SYNTAX_63=Configuration entry \
|
### %s has an invalid value for configuration attribute \
|
### ds-cfg-invalid-attribute-syntax-behavior (it should be one of "accept", \
|
### "reject", or "warn" ): %s
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_PENDING_VALUE_SETS_64=\u914d\u7f6e\u5c5e\u6027 %s \u4f3c\u4e4e\u5305\u542b\u591a\u4e2a\u5f85\u5904\u7406\u7684\u503c\u96c6
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_ACTIVE_VALUE_SETS_65=\u914d\u7f6e\u5c5e\u6027 %s \u4f3c\u4e4e\u5305\u542b\u591a\u4e2a\u6d3b\u52a8\u503c\u96c6
|
MILD_ERR_CONFIG_ATTR_NO_ACTIVE_VALUE_SET_66=\u914d\u7f6e\u5c5e\u6027 %s \u4e0d\u5305\u542b\u6d3b\u52a8\u503c\u96c6
|
MILD_ERR_CONFIG_ATTR_INT_INVALID_TYPE_67=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a\u6574\u6570\u503c\uff0c\u56e0\u4e3a\u8be5\u5143\u7d20\u7684\u7c7b\u578b (%3$s) \u65e0\u6548
|
MILD_ERR_CONFIG_ATTR_INT_INVALID_ARRAY_TYPE_68=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u89e3\u6790\u4e3a\u4e00\u7ec4\u6574\u6570\u503c\uff0c\u56e0\u4e3a\u8be5\u9635\u5217\u5305\u542b\u65e0\u6548\u7c7b\u578b (%s) \u7684\u5143\u7d20
|
MILD_ERR_CONFIG_ATTR_INVALID_STRING_VALUE_69=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a\u5b57\u7b26\u4e32\u503c: %3$s
|
MILD_ERR_CONFIG_ATTR_STRING_INVALID_TYPE_70=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a\u5b57\u7b26\u4e32\u503c\uff0c\u56e0\u4e3a\u8be5\u5143\u7d20\u7684\u7c7b\u578b (%3$s) \u65e0\u6548
|
MILD_ERR_CONFIG_ATTR_STRING_INVALID_ARRAY_TYPE_71=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u89e3\u6790\u4e3a\u4e00\u7ec4\u5b57\u7b26\u4e32\u503c\uff0c\u56e0\u4e3a\u8be5\u9635\u5217\u5305\u542b\u65e0\u6548\u7c7b\u578b (%s) \u7684\u5143\u7d20
|
MILD_ERR_CONFIG_ATTR_INT_WITH_UNIT_INVALID_TYPE_72=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a\u5177\u6709\u5355\u4f4d\u7684\u6574\u6570\u503c\uff0c\u56e0\u4e3a\u8be5\u5143\u7d20\u7684\u7c7b\u578b (%3$s) \u65e0\u6548
|
MILD_ERR_CONFIG_JMX_ATTR_NO_VALUE_73=\u914d\u7f6e\u6761\u76ee %s \u4e0d\u5305\u542b\u5c5e\u6027 %s \u7684\u503c
|
MILD_ERR_CONFIG_JMX_ATTR_NO_ATTR_74=\u914d\u7f6e\u6761\u76ee %s \u4e0d\u5305\u542b\u5c5e\u6027 %s\uff08\u6216\u8005\u8be5\u5c5e\u6027\u5b58\u5728\uff0c\u4f46\u65e0\u6cd5\u901a\u8fc7 JMX \u8fdb\u884c\u8bbf\u95ee\uff09
|
MILD_ERR_CONFIG_JMX_CANNOT_GET_CONFIG_ENTRY_75=\u65e0\u6cd5\u68c0\u7d22\u8981\u901a\u8fc7 JMX \u8fdb\u884c\u8bbf\u95ee\u7684\u914d\u7f6e\u6761\u76ee %s: %s
|
MILD_ERR_CONFIG_JMX_ATTR_INVALID_VALUE_76=\u5c1d\u8bd5\u901a\u8fc7 JMX \u66f4\u65b0\u914d\u7f6e\u6761\u76ee %2$s \u7684\u5c5e\u6027 %1$s \u65f6\u4f1a\u751f\u6210\u65e0\u6548\u7684\u503c: %3$s
|
MILD_ERR_CONFIG_JMX_UNACCEPTABLE_CONFIG_77=\u901a\u8fc7 JMX \u66f4\u65b0\u914d\u7f6e\u6761\u76ee %s \u65f6\u4f1a\u751f\u6210\u65e0\u6548\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_JMX_NO_METHOD_78=\u6ca1\u6709\u7528\u4e8e\u5728\u914d\u7f6e\u6761\u76ee %2$s \u4e2d\u6ce8\u518c\u7684\u4efb\u4f55\u53ef\u8c03\u7528\u7ec4\u4ef6\u7684\u65b9\u6cd5 %1$s
|
MILD_ERR_CONFIG_CANNOT_GET_CONFIG_ENTRY_79=\u5728\u5c1d\u8bd5\u68c0\u7d22\u914d\u7f6e\u6761\u76ee %s \u65f6\u51fa\u73b0\u9519\u8bef: %s
|
INFO_CONFIG_SET_ATTRIBUTE_80=\u5df2\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u5c06\u914d\u7f6e\u5c5e\u6027 %1$s \u7684\u503c\u8bbe\u7f6e\u4e3a %2$s
|
MILD_ERR_CONFIG_CHANGE_NOT_SUCCESSFUL_81=\u66f4\u65b0\u914d\u7f6e\u6761\u76ee %s \u7684\u5c1d\u8bd5\u5931\u8d25\uff0c\u5e76\u9047\u5230\u4e00\u4e2a\u6216\u591a\u4e2a\u95ee\u9898: %s
|
###SEVERE_ERR_CONFIG_LOGGER_NO_FILE_NAME_82=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-log-file which \
|
### specifies the log file name for the associated logger
|
###SEVERE_ERR_CONFIG_JMX_CANNOT_REGISTER_MBEAN_83=The Directory Server could not \
|
### register a JMX MBean for the component associated with configuration entry \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_LDIF_WRITE_ERROR_84=An unexpected error occurred while \
|
### trying to export the Directory Server configuration to LDIF: %s
|
INFO_CONFIG_WORK_QUEUE_DESCRIPTION_NUM_THREADS_85=\u5904\u7406\u8bf7\u6c42\u65f6\u5e94\u4f7f\u7528\u7684\u5de5\u4f5c\u7ebf\u7a0b\u6570\uff08\u7528\u4e8e\u63a7\u5236\u670d\u52a1\u5668\u53ef\u540c\u65f6\u5904\u7406\u7684\u64cd\u4f5c\u6570\uff09\u3002\u6700\u4f73\u503c\u53d6\u51b3\u4e8e\u8fd0\u884c\u670d\u52a1\u5668\u7684\u7cfb\u7edf\u7684\u7c7b\u578b\u4ee5\u53ca\u9700\u8981\u5904\u7406\u7684\u5de5\u4f5c\u8d1f\u8377\uff0c\u6700\u597d\u901a\u8fc7\u6027\u80fd\u6d4b\u8bd5\u6765\u786e\u5b9a\u8be5\u503c\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
INFO_CONFIG_WORK_QUEUE_DESCRIPTION_MAX_CAPACITY_86=\u5728\u4efb\u4e00\u65f6\u523b\uff0c\u5de5\u4f5c\u961f\u5217\u4e2d\u53ef\u4ee5\u4fdd\u7559\u7684\u6700\u5927\u5f85\u5904\u7406\u8bf7\u6c42\u6570\uff08\u6240\u6709\u5de5\u4f5c\u7ebf\u7a0b\u5747\u5fd9\u4e8e\u5904\u7406\u5176\u4ed6\u64cd\u4f5c\uff09\u3002\u5982\u679c\u8fbe\u5230\u8be5\u9650\u5236\uff0c\u5219\u4f1a\u62d2\u7edd\u6240\u6709\u65b0\u8bf7\u6c42\u3002\u5982\u679c\u503c\u4e3a 0\uff0c\u5219\u6307\u793a\u6ca1\u6709\u9650\u5236\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_NUM_WORKER_THREADS_87=An error \
|
### occurred while attempting to retrieve the value of the \
|
### ds-cfg-num-worker-threads attribute from the %s entry, which is used to \
|
### specify the number of worker threads to service the work queue: %s. The \
|
### Directory Server will use the default value of 24
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_QUEUE_CAPACITY_88=An error \
|
### occurred while attempting to retrieve the value of the \
|
### ds-cfg-max-work-queue-capacity attribute from the %s entry, which is used to \
|
### specify the maximum number of pending operations that may be held in the work \
|
### queue: %s. The Directory Server will use the default value of 0
|
###SEVERE_WARN_CONFIG_WORK_QUEUE_NUM_THREADS_INVALID_VALUE_89=The value of \
|
### configuration attribute ds-cfg-num-worker-threads in configuration entry %s \
|
### has an invalid value (%d). This attribute requires an integer value greater \
|
### than zero
|
###SEVERE_WARN_CONFIG_WORK_QUEUE_CAPACITY_INVALID_VALUE_90=The value of \
|
### configuration attribute ds-cfg-max-work-queue-capacity in configuration entry \
|
### %s has an invalid value (%d). This attribute requires an integer value \
|
### greater than or equal to zero
|
INFO_CONFIG_WORK_QUEUE_CREATED_THREADS_91=\u521b\u5efa\u4e86 %d \u4e2a\u989d\u5916\u7684\u5de5\u4f5c\u7ebf\u7a0b\uff0c\u4ee5\u4f7f\u53ef\u7528\u7ebf\u7a0b\u603b\u6570\u53d8\u4e3a %d \u4e2a
|
INFO_CONFIG_WORK_QUEUE_DESTROYING_THREADS_92=\u5c06\u5728\u65b9\u4fbf\u7684\u65f6\u5019\u7acb\u5373\u7ec8\u6b62 %d \u4e2a\u5de5\u4f5c\u7ebf\u7a0b\uff08\u7ebf\u7a0b\u5b9e\u9645\u9000\u51fa\u53ef\u80fd\u9700\u8981\u51e0\u79d2\u949f\u7684\u65f6\u95f4\uff09\uff0c\u4ee5\u4f7f\u53ef\u7528\u7ebf\u7a0b\u603b\u6570\u53d8\u4e3a %d \u4e2a
|
INFO_CONFIG_WORK_QUEUE_NEW_CAPACITY_93=\u66f4\u65b0\u4e86\u5de5\u4f5c\u961f\u5217\u5bb9\u91cf\u4ee5\u4f7f\u7528\u65b0\u503c %d
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURES_94=Worker thread "%s" has \
|
### experienced too many repeated failures while attempting to retrieve the next \
|
### operation from the work queue (%d failures experienced, maximum of %d \
|
### failures allowed). This worker thread will be destroyed
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_CREATE_MONITOR_95=A problem occurred \
|
### while trying to create and start an instance of class %s to use as a monitor \
|
### provider for the Directory Server work queue: %s. No monitor information \
|
### will be available for the work queue
|
INFO_CONFIG_DESCRIPTION_BACKEND_DIRECTORY_96=\u5b58\u50a8\u540e\u7aef\u6570\u636e\u5e93\u6587\u4ef6\u7684\u76ee\u5f55\u7684\u540d\u79f0
|
###SEVERE_ERR_CONFIG_BACKEND_NO_DIRECTORY_97=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-db-directory
|
MILD_ERR_CONFIG_ATTR_DN_NULL_98=\u4e3a DN \u914d\u7f6e\u5c5e\u6027 %s \u63d0\u4f9b\u4e86 Null \u503c
|
MILD_ERR_CONFIG_ATTR_DN_CANNOT_PARSE_99=\u5728\u5c1d\u8bd5\u5c06\u5c5e\u6027 %2$s \u7684\u503c "%1$s" \u89e3\u6790\u4e3a DN \u65f6\u51fa\u73b0\u9519\u8bef: %3$s
|
MILD_ERR_CONFIG_ATTR_INVALID_DN_VALUE_100=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a DN: %3$s
|
MILD_ERR_CONFIG_ATTR_DN_INVALID_TYPE_101=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %2$s \u7684\u503c %1$s \u89e3\u6790\u4e3a DN\uff0c\u56e0\u4e3a\u8be5\u5143\u7d20\u7684\u7c7b\u578b (%3$s) \u65e0\u6548
|
MILD_ERR_CONFIG_ATTR_DN_INVALID_ARRAY_TYPE_102=\u65e0\u6cd5\u5c06\u914d\u7f6e\u5c5e\u6027 %s \u7684\u503c\u89e3\u6790\u4e3a\u4e00\u7ec4 DN \u503c\uff0c\u56e0\u4e3a\u8be5\u9635\u5217\u5305\u542b\u65e0\u6548\u7c7b\u578b (%s) \u7684\u5143\u7d20
|
###FATAL_ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIX_103=An unexpected error \
|
### occurred while trying to register the configuration handler base DN "%s" as a \
|
### private suffix with the Directory Server: %s
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_GET_CONFIG_BASE_104=An error occurred while \
|
### trying to retrieve configuration entry cn=Backends,cn=config in order to \
|
### initialize the Directory Server backends: %s
|
###SEVERE_ERR_CONFIG_BACKEND_BASE_DOES_NOT_EXIST_105=The entry \
|
### cn=Backends,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_BACKEND_ENTRY_DOES_NOT_HAVE_BACKEND_CONFIG_106=Configuration \
|
### entry %s exists below the backend configuration root of cn=Backends,cn=config \
|
### but does not have objectclass ds-cfg-backend that is required for a Directory \
|
### Server backend. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_BACKEND_ERROR_INTERACTING_WITH_BACKEND_ENTRY_107=An \
|
### unexpected error occurred while interacting with backend configuration entry \
|
### %s: %s
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_ENABLED_108=\u6307\u793a\u662f\u5426\u5e94\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u542f\u7528\u8be5\u540e\u7aef\u3002\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8054\u673a\u65f6\u5bf9\u5176\u8fdb\u884c\u66f4\u6539\uff1b\u4f46\u5982\u679c\u7981\u7528\u4e86\u67d0\u4e2a\u540e\u7aef\uff0c\u5219\u5c06\u65e0\u6cd5\u4f7f\u7528\u8be5\u540e\u7aef
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_CLASS_109=\u5e94\u4e3a\u8be5\u540e\u7aef\u5b9e\u73b0\u63d0\u4f9b\u6838\u5fc3\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u540e\u7aef\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_WARN_CONFIG_BACKEND_NO_ENABLED_ATTR_110=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-enabled, which is used to indicate \
|
### whether the backend should be enabled or disabled. Without this attribute, \
|
### it will default to being disabled
|
INFO_CONFIG_BACKEND_DISABLED_111=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u540e\u7aef\u88ab\u6807\u8bb0\u4e3a\u7981\u7528\uff0c\u56e0\u6b64\u4e0d\u4f1a\u4f7f\u7528\u8be5\u540e\u7aef
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATE_112=An unexpected \
|
### error occurred while attempting to determine whether the backend associated \
|
### with configuration entry %s should be enabled or disabled: %s. It will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_BACKEND_NO_CLASS_ATTR_113=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-java-class, which is used to specify the \
|
### name of the class used to provide the backend implementation. The backend \
|
### associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_GET_CLASS_114=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for backend %s: %s. This backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_INSTANTIATE_115=The Directory Server was \
|
### unable to load class %s and use it to create a backend instance as defined in \
|
### configuration entry %s. The error that occurred was: %s. This backend will \
|
### be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_INITIALIZE_116=An error occurred while \
|
### trying to initialize a backend loaded from class %s with the information in \
|
### configuration entry %s: %s. This backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CLASS_NOT_BACKEND_117=The class %s specified in \
|
### configuration entry %s does not contain a valid Directory Server backend \
|
### implementation
|
NOTICE_CONFIG_BACKEND_ACTION_REQUIRED_TO_CHANGE_CLASS_118=\u8bf7\u6c42\u5bf9\u914d\u7f6e\u6761\u76ee %s \u8fdb\u884c\u7684\u66f4\u6539\u5c06\u5bfc\u81f4\u5173\u8054\u540e\u7aef\u7684\u7c7b\u4ece %s \u66f4\u6539\u4e3a %s\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u540e\u7aef\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
NOTICE_CONFIG_BACKEND_CANNOT_REMOVE_BACKEND_WITH_SUBORDINATES_119=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u540e\u7aef\u5177\u6709\u4e00\u4e2a\u6216\u591a\u4e2a\u4ece\u5c5e\u540e\u7aef\u3002\u5982\u679c\u540e\u7aef\u5177\u6709\u4ece\u5c5e\u540e\u7aef\uff0c\u5219\u4e0d\u53ef\u4ee5\u5220\u9664\u8be5\u540e\u7aef
|
INFO_CONFIG_CORE_DESCRIPTION_MAX_ALLOWED_CONNECTIONS_120=\u5728\u4efb\u610f\u7ed9\u5b9a\u65f6\u95f4\uff0c\u53ef\u4ee5\u4e0e\u76ee\u5f55\u670d\u52a1\u5668\u5efa\u7acb\u7684\u6700\u5927\u5ba2\u6237\u7aef\u8fde\u63a5\u6570\u3002\u5982\u679c\u503c\u5c0f\u4e8e\u6216\u7b49\u4e8e\u96f6\uff0c\u5219\u6307\u793a\u6ca1\u6709\u9650\u5236\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
INFO_CONFIG_LOGGER_CLASS_ACTION_REQUIRED_122=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u8bb0\u5f55\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8bb0\u5f55\u5668\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_LOGGER_EXISTS_123=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u8bb0\u5f55\u5668\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u8bb0\u5f55\u5668
|
MILD_ERR_CONFIG_LOGGER_ACCESS_INITIALIZATION_FAILED_124=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8bbf\u95ee\u8bb0\u5f55\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_LOGGER_ERROR_INITIALIZATION_FAILED_125=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u9519\u8bef\u8bb0\u5f55\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_LOGGER_DEBUG_INITIALIZATION_FAILED_126=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8c03\u8bd5\u8bb0\u5f55\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
###FATAL_ERR_CONFIG_MONITOR_CANNOT_GET_BASE_127=An error occurred while \
|
### attempting to retrieve the base monitor entry cn=Monitor Providers,cn=config \
|
### from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_MONITOR_BASE_DOES_NOT_EXIST_128=The monitor configuration \
|
### base cn=Monitor Providers,cn=config does not exist in the Directory Server \
|
### configuration. Only limited monitoring information will be available
|
###SEVERE_ERR_CONFIG_MONITOR_ENTRY_UNACCEPTABLE_129=Configuration entry %s does \
|
### not contain a valid monitor provider configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_MONITOR_CANNOT_CREATE_MONITOR_130=An error occurred while \
|
### attempting to create a Directory Server monitor provider from the information \
|
### in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_OBJECTCLASS_131=Configuration entry %s does \
|
### not contain the ds-cfg-monitor-provider objectclass, which is required for \
|
### monitor provider definitions
|
INFO_CONFIG_MONITOR_DESCRIPTION_CLASS_NAME_132=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u76d1\u89c6\u5668\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u76d1\u89c6\u5668\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_MONITOR_NO_CLASS_NAME_133=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class name \
|
### for the associated monitor provider
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_NAME_134=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_135=Class %s specified in \
|
### configuration entry %s does not contain a valid monitor provider \
|
### implementation: %s
|
INFO_CONFIG_MONITOR_DESCRIPTION_ENABLED_136=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_MONITOR_NO_ENABLED_ATTR_137=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the monitor provider \
|
### should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_ENABLED_VALUE_138=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_MONITOR_CLASS_ACTION_REQUIRED_139=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u76d1\u89c6\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_MONITOR_INITIALIZATION_FAILED_140=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_MONITOR_EXISTS_141=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CONFIG_BASE_142=An error occurred \
|
### while trying to retrieve configuration entry cn=Connection Handlers,cn=config \
|
### in order to initialize the Directory Server backends: %s
|
###SEVERE_ERR_CONFIG_CONNHANDLER_BASE_DOES_NOT_EXIST_143=The entry cn=Connection \
|
### Handlers,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_CONNHANDLER_ENTRY_DOES_NOT_HAVE_CONNHANDLER_CONFIG_144=Configuration \
|
### entry %s exists below the connection handler configuration root of \
|
### cn=Connection Handlers,cn=config but does not have objectclass \
|
### ds-cfg-connection-handler that is required for a Directory Server connection \
|
### handler. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_CONNHANDLER_ERROR_INTERACTING_WITH_CONNHANDLER_ENTRY_145=An \
|
### unexpected error occurred while interacting with connection handler \
|
### configuration entry %s: %s
|
INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_ENABLED_146=\u6307\u793a\u662f\u5426\u5e94\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u542f\u7528\u8be5\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f\u3002\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8054\u673a\u65f6\u5bf9\u5176\u8fdb\u884c\u66f4\u6539\uff1b\u4f46\u5982\u679c\u7981\u7528\u4e86\u67d0\u4e2a\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f\uff0c\u5219\u5c06\u65e0\u6cd5\u4f7f\u7528\u8be5\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f
|
INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_CLASS_147=\u5e94\u4e3a\u8be5\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f\u5b9e\u73b0\u63d0\u4f9b\u6838\u5fc3\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_WARN_CONFIG_CONNHANDLER_NO_ENABLED_ATTR_148=Connection handler \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-enabled, which is used to indicate whether the \
|
### connection handler should be enabled or disabled. Without this attribute, it \
|
### will default to being disabled
|
INFO_CONFIG_CONNHANDLER_DISABLED_149=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f\u88ab\u6807\u8bb0\u4e3a\u7981\u7528\uff0c\u56e0\u6b64\u4e0d\u4f1a\u4f7f\u7528\u8be5\u8fde\u63a5\u5904\u7406\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_CONNHANDLER_UNABLE_TO_DETERMINE_ENABLED_STATE_150=An \
|
### unexpected error occurred while attempting to determine whether the \
|
### connection handler associated with configuration entry %s should be enabled \
|
### or disabled: %s. It will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_NO_CLASS_ATTR_151=Connection handler \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-java-class, which is used to specify the name of the \
|
### class used to provide the connection handler implementation. The connection \
|
### handler associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CLASS_152=An unexpected error \
|
### occurred while trying to determine the name of the Java class that contains \
|
### the implementation for connection handler %s: %s. This connection handler \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INSTANTIATE_153=The Directory Server was \
|
### unable to load class %s and use it to create a connection handler instance as \
|
### defined in configuration entry %s. The error that occurred was: %s. This \
|
### connection handler will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZE_154=An error occurred while \
|
### trying to initialize a connection handler loaded from class %s with the \
|
### information in configuration entry %s: %s. This connection handler will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_UNACCEPTABLE_CONFIG_155=The configuration for \
|
### the connection handler defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_BACKEND_UNACCEPTABLE_CONFIG_156=The configuration for the \
|
### backend defined in configuration entry %s was not acceptable according to its \
|
### internal validation. However, no specific information is available regarding \
|
### the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_MONITOR_UNACCEPTABLE_CONFIG_157=The configuration for the \
|
### monitor provider defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_LOGGER_UNACCEPTABLE_CONFIG_158=The configuration for the \
|
### logger defined in configuration entry %s was not acceptable according to its \
|
### internal validation. However, no specific information is available regarding \
|
### the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CLASS_NOT_CONNHANDLER_159=The class %s \
|
### specified in configuration entry %s does not contain a valid Directory Server \
|
### connection handler implementation
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_MR_BASE_160=An error occurred while \
|
### trying to retrieve configuration entry cn=Matching Rules,cn=config in order \
|
### to initialize the Directory Server matching rules: %s
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_BASE_DOES_NOT_EXIST_161=The entry cn=Matching \
|
### Rules,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_MATCHING_RULES_162=No child entries were found \
|
### below the entry cn=Matching Rules,cn=config to define the matching rules for \
|
### use in the Directory Server. This is an error, because the Directory Server \
|
### must have matching rules defined to function properly
|
###SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_MR_CONFIG_163=Configuration \
|
### entry %s exists below the matching rule configuration root of cn=Matching \
|
### Rules,cn=config but does not have objectclass ds-cfg-matching-rule that is \
|
### required for a Directory Server matching rule. This configuration entry will \
|
### be ignored
|
INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_ENABLED_164=\u6307\u793a\u662f\u5426\u5e94\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u542f\u7528\u8be5\u5339\u914d\u89c4\u5219\u3002\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8054\u673a\u65f6\u5bf9\u5176\u8fdb\u884c\u66f4\u6539\uff1b\u4f46\u5982\u679c\u7981\u7528\u4e86\u67d0\u4e2a\u5339\u914d\u89c4\u5219\uff0c\u5219\u5728\u5c06\u5176\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\u540e\u53ef\u80fd\u65e0\u6cd5\u518d\u6309\u9884\u671f\u65b9\u5f0f\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u6267\u884c\u5339\u914d
|
INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_CLASS_165=\u5e94\u4e3a\u8be5\u5339\u914d\u89c4\u5219\u5b9e\u73b0\u63d0\u4f9b\u6838\u5fc3\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u5339\u914d\u89c4\u5219\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548\u3002\u53e6\u5916\uff0c\u5bf9\u4e8e\u5df2\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\u7684\u5339\u914d\u89c4\u5219\uff0c\u5982\u679c\u66f4\u6539\u5176\u5339\u914d\u89c4\u5219\u7c7b\uff0c\u5219\u5728\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u6267\u884c\u5339\u914d\u65f6\u53ef\u80fd\u4f1a\u4ea7\u751f\u610f\u5916\u7ed3\u679c
|
###SEVERE_WARN_CONFIG_SCHEMA_MR_NO_ENABLED_ATTR_166=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-enabled, which is \
|
### used to indicate whether the matching rule should be enabled or disabled. \
|
### Without this attribute, it will default to being disabled
|
INFO_CONFIG_SCHEMA_MR_DISABLED_167=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5339\u914d\u89c4\u5219\u88ab\u6807\u8bb0\u4e3a\u7981\u7528\uff0c\u56e0\u6b64\u4e0d\u4f1a\u4f7f\u7528\u8be5\u5339\u914d\u89c4\u5219\u5982\u679c\u4e4b\u524d\u5df2\u5c06\u5176\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\uff0c\u5219\u53ef\u80fd\u65e0\u6cd5\u518d\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u7684\u503c\u6267\u884c\u5339\u914d
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_UNABLE_TO_DETERMINE_ENABLED_STATE_168=An \
|
### unexpected error occurred while attempting to determine whether the matching \
|
### rule associated with configuration entry %s should be enabled or disabled: \
|
### %s. It will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_NO_CLASS_ATTR_169=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-java-class, which is used \
|
### to specify the name of the class used to provide the matching rule \
|
### implementation. The matching rule associated with this configuration entry \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_GET_CLASS_170=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for matching rule %s: %s. This matching rule will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INSTANTIATE_171=The Directory Server was \
|
### unable to load class %s and use it to create a matching rule instance as \
|
### defined in configuration entry %s. The error that occurred was: %s. This \
|
### matching rule will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INITIALIZE_172=An error occurred while \
|
### trying to initialize a matching rule loaded from class %s with the \
|
### information in configuration entry %s: %s. This matching rule will be \
|
### disabled
|
###SEVERE_WARN_CONFIG_SCHEMA_MR_CONFLICTING_MR_173=The matching rule defined in \
|
### configuration entry %s conflicts with another matching rule defined in the \
|
### server configuration: %s. This matching rule will not be used
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_SYNTAX_BASE_174=An error occurred while \
|
### trying to retrieve configuration entry cn=Syntaxes,cn=config in order to \
|
### initialize the Directory Server attribute syntaxes: %s
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_BASE_DOES_NOT_EXIST_175=The entry \
|
### cn=Syntaxes,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_SYNTAXES_176=No child entries were found below \
|
### the entry cn=Syntaxes,cn=config to define the attribute syntaxes for use in \
|
### the Directory Server. This is an error, because the Directory Server must \
|
### have syntaxes defined to function properly
|
###SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_SYNTAX_CONFIG_177=Configuration \
|
### entry %s exists below the attribute syntax configuration root of \
|
### cn=Syntaxes,cn=config but does not have objectclass ds-cfg-attribute-syntax \
|
### that is required for a Directory Server attribute syntax. This configuration \
|
### entry will be ignored
|
INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_ENABLED_178=\u6307\u793a\u662f\u5426\u5e94\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u542f\u7528\u8be5\u5c5e\u6027\u8bed\u6cd5\u3002\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8054\u673a\u65f6\u5bf9\u5176\u8fdb\u884c\u66f4\u6539\uff1b\u4f46\u5982\u679c\u5728\u5c06\u67d0\u4e2a\u8bed\u6cd5\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\u540e\u7981\u7528\u4e86\u8be5\u8bed\u6cd5\uff0c\u5219\u53ef\u80fd\u65e0\u6cd5\u518d\u6309\u9884\u671f\u65b9\u5f0f\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u6267\u884c\u5339\u914d
|
INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_CLASS_179=\u5e94\u4e3a\u8be5\u5c5e\u6027\u8bed\u6cd5\u5b9e\u73b0\u63d0\u4f9b\u6838\u5fc3\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8bed\u6cd5\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548\u3002\u53e6\u5916\uff0c\u5bf9\u4e8e\u5df2\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\u7684\u5c5e\u6027\u8bed\u6cd5\uff0c\u5982\u679c\u66f4\u6539\u5176\u8bed\u6cd5\u7c7b\uff0c\u5219\u5728\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u6267\u884c\u5339\u914d\u65f6\u53ef\u80fd\u4f1a\u4ea7\u751f\u610f\u5916\u7ed3\u679c
|
###SEVERE_WARN_CONFIG_SCHEMA_SYNTAX_NO_ENABLED_ATTR_180=Attribute syntax \
|
### configuration entry %s does not contain attribute ds-cfg-enabled, \
|
### which is used to indicate whether the syntax should be enabled or disabled. \
|
### Without this attribute, it will default to being disabled
|
INFO_CONFIG_SCHEMA_SYNTAX_DISABLED_181=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5c5e\u6027\u8bed\u6cd5\u88ab\u6807\u8bb0\u4e3a\u7981\u7528\uff0c\u56e0\u6b64\u4e0d\u4f1a\u4f7f\u7528\u8be5\u5c5e\u6027\u8bed\u6cd5\u3002\u5982\u679c\u4e4b\u524d\u5df2\u5c06\u5176\u7528\u4e8e\u4e00\u4e2a\u6216\u591a\u4e2a\u5c5e\u6027\uff0c\u5219\u53ef\u80fd\u65e0\u6cd5\u518d\u5bf9\u8fd9\u4e9b\u5c5e\u6027\u7684\u503c\u6267\u884c\u5339\u914d
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_UNABLE_TO_DETERMINE_ENABLED_STATE_182=An \
|
### unexpected error occurred while attempting to determine whether the attribute \
|
### syntax associated with configuration entry %s should be enabled or disabled: \
|
### %s. It will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_NO_CLASS_ATTR_183=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-java-class, which is used to \
|
### specify the name of the class that provides the attribute syntax \
|
### implementation. The syntax associated with this configuration entry will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_GET_CLASS_184=An unexpected error \
|
### occurred while trying to determine the name of the Java class that contains \
|
### the implementation for attribute syntax %s: %s. This syntax will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INSTANTIATE_185=The Directory Server \
|
### was unable to load class %s and use it to create an attribute syntax instance \
|
### as defined in configuration entry %s. The error that occurred was: %s. \
|
### This syntax will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INITIALIZE_186=An error occurred while \
|
### trying to initialize an attribute syntax loaded from class %s with the \
|
### information in configuration entry %s: %s. This syntax will be disabled
|
###SEVERE_WARN_CONFIG_SCHEMA_SYNTAX_CONFLICTING_SYNTAX_187=The attribute syntax \
|
### defined in configuration entry %s conflicts with another syntax defined in \
|
### the server configuration: %s. This attribute syntax will not be used
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_SCHEMA_DIR_188=Unable to read the Directory \
|
### Server schema definitions because the schema directory %s does not exist
|
###SEVERE_ERR_CONFIG_SCHEMA_DIR_NOT_DIRECTORY_189=Unable to read the Directory \
|
### Server schema definitions because the schema directory %s exists but is not a \
|
### directory
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_LIST_FILES_190=Unable to read the Directory \
|
### Server schema definitions from directory %s or %s because an unexpected error \
|
### occurred while trying to list the files in that directory: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_OPEN_FILE_191=Schema configuration file %s \
|
### in directory %s cannot be parsed because an unexpected error occurred while \
|
### trying to open the file for reading: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_READ_LDIF_ENTRY_192=Schema configuration \
|
### file %s in directory %s cannot be parsed because an unexpected error occurred \
|
### while trying to read its contents as an LDIF entry: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_ATTR_TYPE_193=Unable to parse an \
|
### attribute type definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_ATTR_TYPE_194=An attribute type read \
|
### from schema configuration file %s conflicts with another attribute type \
|
### already read into the schema: %s. The later attribute type definition will \
|
### be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_OC_195=An objectclass read from schema \
|
### configuration file %s conflicts with another objectclass already read into \
|
### the schema: %s. The later objectclass definition will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_OC_196=An objectclass read from schema \
|
### configuration file %s could not be parsed: %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_STRUCTURAL_CLASS_BEHAVIOR_197=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-single-structural-objectclass-behavior (it should be one of "accept", \
|
### "reject", or "warn" ): %s
|
INFO_CONFIG_CORE_DESCRIPTION_CHECK_SCHEMA_198=\u6307\u793a\u76ee\u5f55\u670d\u52a1\u5668\u662f\u5426\u5e94\u6839\u636e\u670d\u52a1\u5668\u7684\u6a21\u5f0f\u914d\u7f6e\uff0c\u5bf9\u66f4\u65b0\u64cd\u4f5c\u6267\u884c\u6a21\u5f0f\u68c0\u67e5\u4ee5\u786e\u4fdd\u8fd9\u4e9b\u6761\u76ee\u6709\u6548\uff08\u4f8b\u5982\uff0c\u5305\u542b\u6240\u6709\u5fc5\u9700\u5c5e\u6027\u5e76\u4e14\u6ca1\u6709\u7981\u6b62\u7684\u5c5e\u6027\uff09\u3002\u901a\u5e38\uff0c\u4e0d\u5efa\u8bae\u60a8\u7981\u7528\u6a21\u5f0f\u68c0\u67e5\uff0c\u56e0\u4e3a\u8fd9\u6837\u53ef\u80fd\u4f7f\u670d\u52a1\u5668\u4e2d\u5305\u542b\u65e0\u6548\u6761\u76ee\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_CHECK_SCHEMA_199=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-check-schema (it should be a \
|
### Boolean value of true or false): %s
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHE_200=An unexpected \
|
### error occurred that prevented the server from installing its default entry \
|
### cache framework: %s
|
###SEVERE_WARN_CONFIG_ENTRYCACHE_NO_CONFIG_ENTRY_201=The entry cache \
|
### configuration entry "cn=Entry Caches,cn=config" does not exist in the \
|
### Directory Server configuration. No entry cache will be available until this \
|
### entry is created with a valid entry cache configuration
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHE_202=An error occurred \
|
### while attempting to initialize an instance of class %s for use as the \
|
### Directory Server entry cache: %s. As a result, the entry cache will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLE_203=The configuration for \
|
### the entry cache defined in configuration entry %s was not acceptable: %s
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLE_204=The configuration \
|
### for the entry cache defined in configuration entry %s was not acceptable: \
|
### the entry cache level %d is already in use
|
INFO_WARN_CONFIG_ENTRYCACHE_NO_MONITOR_CONFIG_ENTRY_205=\u6761\u76ee\u7f13\u5b58 %s \u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e\u4e0d\u53ef\u7528\u3002\u56e0\u6b64\uff0c\u5c06\u4e0d\u4f1a\u542f\u7528\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f %s
|
INFO_WARN_CONFIG_ENTRYCACHE_MONITOR_CONFIG_DISABLED_206=\u5df2\u7981\u7528\u6761\u76ee\u7f13\u5b58 %s \u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e\u3002\u56e0\u6b64\uff0c\u5c06\u4e0d\u4f1a\u542f\u7528\u76d1\u89c6\u5668\u63d0\u4f9b\u7a0b\u5e8f %s
|
MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_CHILD_215=\u5728\u5c1d\u8bd5\u5c06\u6761\u76ee %s \u4f5c\u4e3a\u914d\u7f6e\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u5220\u9664\u65f6\u51fa\u73b0\u610f\u5916\u9519\u8bef: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_NAME_FORM_216=Unable to parse a name \
|
### form definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_NAME_FORM_217=A name form read from \
|
### schema configuration file %s conflicts with another name form already read \
|
### into the schema: %s. The later name form definition will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_DCR_218=Unable to parse a DIT content \
|
### rule definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_DCR_219=A DIT content rule read from \
|
### schema configuration file %s conflicts with another DIT content rule already \
|
### read into the schema: %s. The later DIT content rule definition will be \
|
### used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_DSR_220=Unable to parse a DIT \
|
### structure rule definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_DSR_221=A DIT structure rule read from \
|
### schema configuration file %s conflicts with another DIT structure rule \
|
### already read into the schema: %s. The later DIT structure rule definition \
|
### will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_MRU_222=Unable to parse a matching \
|
### rule use definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_MRU_223=A matching rule use read from \
|
### schema configuration file %s conflicts with another matching rule use already \
|
### read into the schema: %s. The later matching rule use definition will be \
|
### used
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ROTATION_POLICY_224=No file rotation policy has \
|
### been defined in configuration entry %s. No log rotation will take place
|
###SEVERE_ERR_CONFIG_LOGGER_NO_SIZE_LIMIT_225=No size limit has been defined for \
|
### the size based file rotation policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_NO_TIME_LIMIT_226=No time limit has been defined for \
|
### the time based file rotation policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ROTATION_POLICY_227=An invalid file rotation \
|
### policy %s has been defined in configuration entry %s
|
MILD_ERR_CONFIG_ATTR_READ_ONLY_228=\u914d\u7f6e\u5c5e\u6027 %s \u4e3a\u53ea\u8bfb\u5c5e\u6027\uff0c\u4e0d\u53ef\u4ee5\u66f4\u6539\u8be5\u5c5e\u6027\u7684\u503c
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CONFIG_BASE_229=An error occurred while \
|
### trying to retrieve configuration entry cn=Plugins,cn=config in order to \
|
### initialize the Directory Server plugins: %s
|
###SEVERE_ERR_CONFIG_PLUGIN_BASE_DOES_NOT_EXIST_230=The entry \
|
### cn=Plugins,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_PLUGIN_ENTRY_DOES_NOT_HAVE_PLUGIN_CONFIG_231=Configuration \
|
### entry %s exists below the plugin configuration root of cn=Plugins,cn=config \
|
### but does not have objectclass ds-cfg-backend that is required for a Directory \
|
### Server plugin. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_PLUGIN_ERROR_INTERACTING_WITH_PLUGIN_ENTRY_232=An \
|
### unexpected error occurred while interacting with backend configuration entry \
|
### %s: %s
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_ENABLED_233=\u6307\u793a\u662f\u5426\u5e94\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u542f\u7528\u8be5\u63d2\u4ef6\u3002\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8054\u673a\u65f6\u5bf9\u5176\u8fdb\u884c\u66f4\u6539\uff0c\u6240\u505a\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_WARN_CONFIG_PLUGIN_NO_ENABLED_ATTR_234=Plugin configuration entry %s \
|
### does not contain attribute ds-cfg-enabled, which is used to indicate \
|
### whether the plugin should be enabled or disabled. Without this attribute, it \
|
### will default to being disabled
|
INFO_CONFIG_PLUGIN_DISABLED_235=\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u63d2\u4ef6\u88ab\u6807\u8bb0\u4e3a\u7981\u7528\uff0c\u56e0\u6b64\u4e0d\u4f1a\u4f7f\u7528\u8be5\u63d2\u4ef6
|
###SEVERE_ERR_CONFIG_PLUGIN_UNABLE_TO_DETERMINE_ENABLED_STATE_236=An unexpected \
|
### error occurred while attempting to determine whether the plugin associated \
|
### with configuration entry %s should be enabled or disabled: %s. It will be \
|
### disabled
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_PLUGIN_TYPE_237=\u8be5\u63d2\u4ef6\u7684\u63d2\u4ef6\u7c7b\u578b\uff0c\u7528\u4e8e\u63a7\u5236\u5728\u5904\u7406\u671f\u95f4\u8c03\u7528\u8be5\u63d2\u4ef6\u7684\u65f6\u95f4\u3002\u4ec5\u5728\u52a0\u8f7d\u5e76\u521d\u59cb\u5316\u63d2\u4ef6\u65f6\u624d\u4f1a\u8bfb\u53d6\u8be5\u503c\uff0c\u56e0\u6b64\uff0c\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u63d2\u4ef6\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_CLASS_238=\u5e94\u4e3a\u8be5\u63d2\u4ef6\u5b9e\u73b0\u63d0\u4f9b\u6838\u5fc3\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u63d2\u4ef6\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_ERR_CONFIG_PLUGIN_NO_PLUGIN_TYPES_239=Plugin configuration entry %s \
|
### does not contain attribute ds-cfg-plugin-type, which is used to specify the \
|
### name(s) of the plugin type(s) for the plugin. This is a required attribute, \
|
### so this plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_INVALID_PLUGIN_TYPE_240=Plugin configuration entry \
|
### %s has an invalid value %s for attribute ds-cfg-plugin-type that does not \
|
### name a valid plugin type. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_PLUGIN_TYPES_241=An unexpected error \
|
### occurred while trying to determine the set of plugin types for the plugin \
|
### defined in configuration entry %s: %s. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_NO_CLASS_ATTR_242=Plugin configuration entry %s does \
|
### not contain attribute ds-cfg-java-class, which is used to specify the name \
|
### of the class used to provide the plugin implementation. The plugin \
|
### associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CLASS_243=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for plugin %s: %s. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INSTANTIATE_244=The Directory Server was \
|
### unable to load class %s and use it to create a plugin instance as defined in \
|
### configuration entry %s. The error that occurred was: %s. This plugin will \
|
### be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INITIALIZE_245=An error occurred while \
|
### attempting to initialize an instance of class %s as a Directory Server plugin \
|
### using the information in configuration entry %s: %s. This plugin will be \
|
### disabled
|
INFO_CONFIG_CORE_DESCRIPTION_NOTIFY_ABANDONED_OPERATIONS_246=\u6307\u793a\u76ee\u5f55\u670d\u52a1\u5668\u662f\u5426\u5e94\u5c06\u5bf9\u5df2\u653e\u5f03\u64cd\u4f5c\u7684\u54cd\u5e94\u53d1\u9001\u5230\u5ba2\u6237\u7aef\uff0c\u4ee5\u4f7f\u5176\u4e86\u89e3\u670d\u52a1\u5668\u5df2\u5b8c\u6210\u5bf9\u8fd9\u4e9b\u64cd\u4f5c\u7684\u5904\u7406\u3002LDAP \u89c4\u8303\u7981\u6b62\u5728\u8fd9\u4e9b\u60c5\u51b5\u4e0b\u53d1\u9001\u54cd\u5e94\uff1b\u4f46\u5982\u679c\u56e0\u4e3a\u653e\u5f03\u4e86\u67d0\u9879\u64cd\u4f5c\u81f4\u4f7f\u5176\u6ca1\u6709\u4efb\u4f55\u54cd\u5e94\uff0c\u800c\u67d0\u4e9b\u5ba2\u6237\u7aef\u5374\u5728\u7b49\u5f85\u8be5\u64cd\u4f5c\u7684\u54cd\u5e94\uff0c\u5219\u8fd9\u4e9b\u5ba2\u6237\u7aef\u53ef\u80fd\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_NOTIFY_ABANDONED_OPERATIONS_247=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-notify-abandoned-operations (it should be a Boolean value of true or \
|
### false): %s
|
###SEVERE_ERR_CONFIG_EXTOP_INVALID_CLASS_256=Class %s specified in configuration \
|
### entry %s does not contain a valid extended operation handler implementation: \
|
### %s
|
MILD_ERR_CONFIG_EXTOP_INITIALIZATION_FAILED_261=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u6269\u5c55\u64cd\u4f5c\u5904\u7406\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
###FATAL_ERR_CONFIG_SASL_CANNOT_GET_BASE_264=An error occurred while attempting \
|
### to retrieve the SASL mechanism handler base entry cn=SASL \
|
### Mechanisms,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_SASL_BASE_DOES_NOT_EXIST_265=The SASL mechanism \
|
### configuration base cn=SASL Mechanisms,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_SASL_ENTRY_UNACCEPTABLE_266=Configuration entry %s does not \
|
### contain a valid SASL mechanism handler configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_SASL_CANNOT_CREATE_HANDLER_267=An error occurred while \
|
### attempting to create a Directory Server SASL mechanism handler from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_SASL_INVALID_OBJECTCLASS_268=Configuration entry %s does \
|
### not contain the ds-cfg-sasl-mechanism-handler objectclass, which is required \
|
### for SASL mechanism handler definitions
|
INFO_CONFIG_SASL_DESCRIPTION_CLASS_NAME_269=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u5904\u7406\u7a0b\u5e8f\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u5904\u7406\u7a0b\u5e8f\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_SASL_NO_CLASS_NAME_270=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated SASL mechanism handler
|
###SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_NAME_271=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_272=Class %s specified in configuration \
|
### entry %s does not contain a valid SASL mechanism handler implementation: %s
|
INFO_CONFIG_SASL_DESCRIPTION_ENABLED_273=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_SASL_NO_ENABLED_ATTR_274=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the SASL \
|
### mechanism handler should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_SASL_INVALID_ENABLED_VALUE_275=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_SASL_CLASS_ACTION_REQUIRED_276=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u5904\u7406\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_SASL_INITIALIZATION_FAILED_277=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_SASL_EXISTS_278=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u5904\u7406\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_SASL_UNACCEPTABLE_CONFIG_279=The configuration for the SASL \
|
### mechanism handler defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
MILD_ERR_CONFIG_FILE_ADD_ALREADY_EXISTS_280=\u65e0\u6cd5\u5c06\u6761\u76ee %s \u6dfb\u52a0\u5230\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\uff0c\u56e0\u4e3a\u5df2\u5b58\u5728\u53e6\u4e00\u4e2a\u5177\u6709\u8be5 DN \u7684\u914d\u7f6e\u6761\u76ee
|
MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_DN_281=\u65e0\u6cd5\u5c06\u6761\u76ee %s \u6dfb\u52a0\u5230\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\uff0c\u56e0\u4e3a\u8be5 DN \u6ca1\u6709\u7236 DN
|
MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_282=\u65e0\u6cd5\u5c06\u6761\u76ee %s \u6dfb\u52a0\u5230\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\uff0c\u56e0\u4e3a\u5176\u7236\u6761\u76ee %s \u4e0d\u5b58\u5728
|
MILD_ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENER_283=\u76ee\u5f55\u670d\u52a1\u5668\u65e0\u6cd5\u6dfb\u52a0\u914d\u7f6e\u6761\u76ee %s\uff0c\u56e0\u4e3a\u7236\u6761\u76ee %s \u4e2d\u6ce8\u518c\u7684\u67d0\u4e2a\u6dfb\u52a0\u4fa6\u542c\u5668\u62d2\u7edd\u6b64\u66f4\u6539\u5e76\u663e\u793a\u4ee5\u4e0b\u6d88\u606f: %s
|
MILD_ERR_CONFIG_FILE_ADD_FAILED_284=\u5728\u5c1d\u8bd5\u5c06\u914d\u7f6e\u6761\u76ee %s \u6dfb\u52a0\u4e3a\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u65f6\u51fa\u73b0\u610f\u5916\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_DELETE_NO_SUCH_ENTRY_285=\u65e0\u6cd5\u4ece\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5220\u9664\u6761\u76ee %s\uff0c\u56e0\u4e3a\u6307\u5b9a\u7684\u6761\u76ee\u4e0d\u5b58\u5728
|
MILD_ERR_CONFIG_FILE_DELETE_HAS_CHILDREN_286=\u65e0\u6cd5\u4ece\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5220\u9664\u6761\u76ee %s\uff0c\u56e0\u4e3a\u6307\u5b9a\u7684\u6761\u76ee\u5177\u6709\u4e00\u4e2a\u6216\u591a\u4e2a\u4e0b\u7ea7\u6761\u76ee
|
MILD_ERR_CONFIG_FILE_DELETE_NO_PARENT_287=\u65e0\u6cd5\u4ece\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5220\u9664\u6761\u76ee %s\uff0c\u56e0\u4e3a\u8be5\u6761\u76ee\u6ca1\u6709\u7236\u6761\u76ee\uff0c\u5e76\u4e14\u4e0d\u5141\u8bb8\u5220\u9664\u914d\u7f6e\u6839\u6761\u76ee
|
MILD_ERR_CONFIG_FILE_DELETE_REJECTED_288=\u65e0\u6cd5\u4ece\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5220\u9664\u6761\u76ee %s\uff0c\u56e0\u4e3a\u7236\u6761\u76ee %s \u4e2d\u6ce8\u518c\u7684\u67d0\u4e2a\u5220\u9664\u4fa6\u542c\u5668\u62d2\u7edd\u6b64\u66f4\u6539\u5e76\u663e\u793a\u4ee5\u4e0b\u6d88\u606f: %s
|
MILD_ERR_CONFIG_FILE_DELETE_FAILED_289=\u5728\u5c1d\u8bd5\u5c06\u914d\u7f6e\u6761\u76ee %s \u4f5c\u4e3a\u6761\u76ee %s \u7684\u5b50\u6761\u76ee\u5220\u9664\u65f6\u51fa\u73b0\u610f\u5916\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_MODIFY_NO_SUCH_ENTRY_290=\u65e0\u6cd5\u4fee\u6539\u6761\u76ee %s\uff0c\u56e0\u4e3a\u6307\u5b9a\u7684\u6761\u76ee\u4e0d\u5b58\u5728
|
MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENER_291=\u65e0\u6cd5\u4fee\u6539\u6761\u76ee %s\uff0c\u56e0\u4e3a\u4e3a\u8be5\u6761\u76ee\u6ce8\u518c\u7684\u67d0\u4e2a\u914d\u7f6e\u66f4\u6539\u4fa6\u542c\u5668\u62d2\u7edd\u6b64\u66f4\u6539: %s
|
MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_COMPONENT_292=\u65e0\u6cd5\u4fee\u6539\u6761\u76ee %s\uff0c\u56e0\u4e3a\u4e3a\u8be5\u6761\u76ee\u6ce8\u518c\u7684\u67d0\u4e2a\u53ef\u914d\u7f6e\u7ec4\u4ef6\u62d2\u7edd\u6b64\u66f4\u6539: %s
|
MILD_ERR_CONFIG_FILE_SEARCH_NO_SUCH_BASE_293=\u65e0\u6cd5\u5904\u7406\u641c\u7d22\u64cd\u4f5c\uff0c\u56e0\u4e3a\u57fa\u6761\u76ee %s \u4e0d\u5b58\u5728
|
MILD_ERR_CONFIG_FILE_SEARCH_INVALID_SCOPE_294=\u65e0\u6cd5\u5904\u7406\u641c\u7d22\u64cd\u4f5c\uff0c\u56e0\u4e3a\u6307\u5b9a\u7684\u641c\u7d22\u8303\u56f4 %s \u65e0\u6548
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_CREATE_TEMP_ARCHIVE_295=\u56e0\u914d\u7f6e\u66f4\u6539\u800c\u5c1d\u8bd5\u521b\u5efa\u4e34\u65f6\u6587\u4ef6 %s \u4ee5\u4fdd\u5b58\u4ee5\u524d\u7684\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u7684\u5f52\u6863\u7248\u672c\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_EXISTING_ARCHIVE_296=\u5728\u5c1d\u8bd5\u5c06\u5f52\u6863\u914d\u7f6e\u4ece %s \u590d\u5236\u5230\u4e34\u65f6\u6587\u4ef6 %s \u4e2d\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_CURRENT_CONFIG_297=\u5728\u5c1d\u8bd5\u66f4\u65b0\u6587\u4ef6 %s \u4e2d\u7684\u5f52\u6863\u914d\u7f6e\u4ee5\u5305\u542b\u6587\u4ef6 %s \u4e2d\u6b63\u5728\u8fd0\u884c\u7684\u914d\u7f6e\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_TEMP_ARCHIVE_298=\u5c06\u5f52\u6863\u914d\u7f6e\u6570\u636e\u4ece %s \u91cd\u547d\u540d\u4e3a %s \u7684\u5c1d\u8bd5\u5931\u8d25\uff0c\u4f46\u65e0\u6cd5\u786e\u5b9a\u5931\u8d25\u7684\u6839\u672c\u539f\u56e0
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_REPLACE_ARCHIVE_299=\u65e0\u6cd5\u5c06\u5305\u542b\u4ee5\u524d\u7684\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u7684\u66f4\u65b0\u5f52\u6863\u6587\u4ef6\u4ece %s \u91cd\u547d\u540d\u4e3a %s: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIG_300=\u5728\u5c1d\u8bd5\u5c06\u65b0\u7684\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u5bfc\u51fa\u5230\u6587\u4ef6 %s \u4e2d\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIG_301=\u5728\u5c1d\u8bd5\u5c06\u65b0\u7684\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4ece\u6587\u4ef6 %s \u91cd\u547d\u540d\u4e3a %s \u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_FILE_MODDN_NOT_ALLOWED_302=\u4e0d\u5141\u8bb8\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u4fee\u6539 DN \u64cd\u4f5c
|
INFO_CONFIG_LOGGER_SUPPRESS_INTERNAL_OPERATIONS_303=\u6307\u793a\u662f\u5426\u5e94\u5c06\u5185\u90e8\u64cd\u4f5c\u7684\u6d88\u606f\u4ece\u8bbf\u95ee\u65e5\u5fd7\u6587\u4ef6\u4e2d\u6392\u9664
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_SUPPRESS_INT_OPERATION_VALUE_304=Invalid \
|
### value specified for attribute %s. Allowed values are true or false
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BASE_DNS_305=\u5e94\u8be5\u7528\u4e8e\u8be5\u540e\u7aef\u7684\u57fa DN \u96c6\u3002\u5bf9\u8be5\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u662f\u5426\u81ea\u52a8\u751f\u6548\u53d6\u51b3\u4e8e\u540e\u7aef\u5b9e\u73b0
|
###SEVERE_ERR_CONFIG_BACKEND_NO_BASE_DNS_306=Backend configuration entry %s does \
|
### not contain attribute ds-cfg-base-dn, which is used to specify the \
|
### set of base DNs for the backend. This is a required attribute, and therefore \
|
### the backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BASE_DNS_307=An unexpected \
|
### error occurred while attempting to determine the set of base DNs associated \
|
### with the backend defined in configuration entry %s: %s. This backend will \
|
### be disabled
|
INFO_CONFIG_KEYMANAGER_DESCRIPTION_ENABLED_313=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u3002\u9700\u8981\u8bbf\u95ee\u5bc6\u94a5\u7ba1\u7406\u5668\u7684\u64cd\u4f5c\uff08\u5982\u901a\u8fc7 SSL \u8fdb\u884c\u7684\u901a\u4fe1\uff09\u90fd\u8981\u6c42\u4f7f\u7528\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u3002\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548\uff0c\u4f46\u4ec5\u5f71\u54cd\u4ee5\u540e\u8bbf\u95ee\u5bc6\u94a5\u7ba1\u7406\u5668\u7684\u5c1d\u8bd5
|
###SEVERE_ERR_CONFIG_KEYMANAGER_NO_ENABLED_ATTR_314=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the key manager provider is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_KEYMANAGER_DESCRIPTION_CLASS_317=Fully-qualified name of the \
|
### Java class that includes the key manager provider \
|
### implementation. Changes to this configuration attribute will not take effect \
|
### until the key manager provider has been disabled and then re-enabled, or \
|
### until the server is restarted
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_ENABLED_328=Indicates whether the \
|
### Directory Server trust manager provider should be enabled. A trust manager \
|
### provider is required for operations that require access to a trust manager \
|
### (e.g., communication over SSL). Changes to this configuration attribute will \
|
### take effect immediately, but will only impact future attempts to access the \
|
### trust manager
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_ENABLED_ATTR_329=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the trust manager provider is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_CLASS_332=Fully-qualified name of the \
|
### Java class that includes the trust manager \
|
### provider implementation. Changes to this configuration attribute will not \
|
### take effect until the trust manager provider has been disabled and then \
|
### re-enabled, or until the server is restarted
|
###SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_ENABLED_347=Indicates whether the \
|
### Directory Server certificate mapper should be enabled. A certificate mapper \
|
### is used to establish a mapping between a client certificate chain and a user \
|
### entry in the Directory Server for SASL EXTERNAL authentication and similar \
|
### purposes. Changes to this configuration attribute will take effect \
|
### immediately
|
###SEVERE_ERR_CONFIG_CERTMAPPER_NO_ENABLED_ATTR_348=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the certificate mapper is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_CLASS_351=Fully-qualified name of the \
|
### Java class that includes the certificate mapper \
|
### implementation. Changes to this configuration attribute will not take effect \
|
### until the certificate mapper has been disabled and then re-enabled, or until \
|
### the server is restarted
|
MILD_WARN_CONFIG_LOGGER_NO_RETENTION_POLICY_357=\u672a\u5728\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u4efb\u4f55\u6587\u4ef6\u4fdd\u7559\u7b56\u7565\u3002\u5c06\u4e0d\u4f1a\u5220\u9664\u4efb\u4f55\u65e5\u5fd7\u6587\u4ef6
|
###SEVERE_WARN_CONFIG_LOGGER_INVALID_RETENTION_POLICY_358=An invalid file \
|
### retention policy %s has been defined in configuration entry %s
|
###SEVERE_WARN_CONFIG_LOGGER_NO_NUMBER_OF_FILES_359=No file number limit has \
|
### been defined for the retention policy in the configuration entry %s
|
###SEVERE_WARN_CONFIG_LOGGER_NO_DISK_SPACE_USED_360=No disk space limit has been \
|
### defined for the retention policy in the configuration entry %s
|
###FATAL_ERR_CONFIG_PWSCHEME_CANNOT_GET_BASE_363=An error occurred while \
|
### attempting to retrieve the password storage scheme base entry cn=Password \
|
### Storage Schemes,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWSCHEME_BASE_DOES_NOT_EXIST_364=The password storage \
|
### scheme configuration base cn=Password Storage Schemes,cn=config does not \
|
### exist in the Directory Server configuration. This entry must be present for \
|
### the server to function properly
|
###SEVERE_ERR_CONFIG_PWSCHEME_ENTRY_UNACCEPTABLE_365=Configuration entry %s does \
|
### not contain a valid password storage scheme configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWSCHEME_CANNOT_CREATE_SCHEME_366=An error occurred while \
|
### attempting to create a Directory Server password storage scheme from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_OBJECTCLASS_367=Configuration entry %s \
|
### does not contain the ds-cfg-password-storage-scheme objectclass, which is \
|
### required for password storage scheme definitions
|
INFO_CONFIG_PWSCHEME_DESCRIPTION_CLASS_NAME_368=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u65b9\u6848\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u5b58\u50a8\u65b9\u6848\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWSCHEME_NO_CLASS_NAME_369=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified \
|
### class name for the associated password storage scheme
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_NAME_370=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_371=Class %s specified in \
|
### configuration entry %s does not contain a valid password storage scheme \
|
### implementation: %s
|
INFO_CONFIG_PWSCHEME_DESCRIPTION_ENABLED_372=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWSCHEME_NO_ENABLED_ATTR_373=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### storage scheme should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_ENABLED_VALUE_374=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: \
|
### %s
|
INFO_CONFIG_PWSCHEME_CLASS_ACTION_REQUIRED_375=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u5b58\u50a8\u65b9\u6848\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED_376=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_PWSCHEME_EXISTS_377=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u5b58\u50a8\u65b9\u6848
|
###SEVERE_ERR_CONFIG_PWSCHEME_UNACCEPTABLE_CONFIG_378=The configuration for the \
|
### password storage scheme defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_PLUGIN_CLASS_ACTION_REQUIRED_379=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u63d2\u4ef6\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u63d2\u4ef6\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_ERR_CONFIG_LOGGER_NO_FREE_DISK_SPACE_380=No disk space limit has been \
|
### defined for the retention policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_JAVA5_POLICY_381=The free disk space based \
|
### retention policy in the configuration entry %s. is not allowed for the \
|
### Directory Server when running on pre Java 6 VMs
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BACKEND_ID_382=\u8be5\u540e\u7aef\u7684\u552f\u4e00\u6807\u8bc6\u7b26\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u540e\u7aef\u6216\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\uff0c\u5bf9\u8be5\u914d\u7f6e\u5c5e\u6027\u6240\u505a\u7684\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_WARN_CONFIG_BACKEND_NO_BACKEND_ID_383=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-backend-id, which is used to provide a \
|
### unique identifier for the backend. The backend will be disabled
|
###SEVERE_WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_ID_384=The backend defined in \
|
### configuration entry %s has a backend ID of %s that conflicts with the backend \
|
### ID for another backend in the server. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BACKEND_ID_385=An unexpected \
|
### error occurred while attempting to determine the backend ID for the backend \
|
### defined in configuration entry %s: %s. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_MAC_386=An error occurred while \
|
### attempting to obtain the %s MAC provider to create the signed hash for the \
|
### backup: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_DIGEST_387=An error occurred while \
|
### attempting to obtain the %s message digest to create the hash for the backup: \
|
### %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_388=An error occurred \
|
### while trying to create the config archive file %s in directory %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_CIPHER_389=An error occurred while \
|
### attempting to obtain the cipher to use to encrypt the backup: %s
|
###SEVERE_ERR_CONFIG_BACKUP_ZIP_COMMENT_390=%s config backup %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_DETERMINE_CONFIG_FILE_LOCATION_391=An error \
|
### occurred while attempting to determine the path to the Directory Server \
|
### configuration file so that it could be archived: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_BACKUP_CONFIG_FILE_392=An error occurred \
|
### while attempting to back up configuration file %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_BACKUP_ARCHIVED_CONFIGS_393=An error occurred \
|
### while attempting to back up the archived previous configurations from file \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_CLOSE_ZIP_STREAM_394=An error occurred while \
|
### trying to close the config archive file %s in directory %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_395=An error \
|
### occurred while attempting to update the backup descriptor file %s with \
|
### information about the configuration backup: %s
|
###SEVERE_ERR_CONFIG_RESTORE_NO_SUCH_BACKUP_396=Unable to restore or verify \
|
### configuration backup %s in directory %s because no such backup exists
|
###SEVERE_ERR_CONFIG_RESTORE_NO_BACKUP_FILE_397=Unable to restore or verify \
|
### configuration backup %s in directory %s because the archive filename could \
|
### not be determined
|
###SEVERE_ERR_CONFIG_RESTORE_NO_SUCH_FILE_398=Unable to restore or verify \
|
### configuration backup %s because the specified archive file %s does not exist
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CHECK_FOR_ARCHIVE_399=Unable to restore or \
|
### verify configuration backup %s because an error occurred while trying to \
|
### determine whether backup archive %s exists: %s
|
###SEVERE_ERR_CONFIG_RESTORE_UNKNOWN_DIGEST_400=Unable to restore or verify \
|
### configuration backup %s because an unsigned hash of this backup is available \
|
### but the server cannot determine the digest algorithm used to generate this \
|
### hash
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_DIGEST_401=Unable to restore or verify \
|
### configuration backup %s because it has an unsigned hash that uses an unknown \
|
### or unsupported digest algorithm of %s
|
###SEVERE_ERR_CONFIG_RESTORE_UNKNOWN_MAC_402=Unable to restore or verify \
|
### configuration backup %s because a signed hash of this backup is available but \
|
### the server cannot determine the MAC algorithm used to generate this hash
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_MAC_403=Unable to restore or verify \
|
### configuration backup %s because it has a signed hash that uses an unknown or \
|
### unsupported MAC algorithm of %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_OPEN_BACKUP_FILE_404=Unable to restore or \
|
### verify configuration backup %s because an error occurred while attempting to \
|
### open the backup archive file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_CIPHER_406=Unable to restore or verify \
|
### configuration backup %s because it is encrypted using an unknown or \
|
### unsupported cipher: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_BACKUP_EXISTING_CONFIG_407=Unable to restore \
|
### configuration backup %s because an error occurred while attempting to \
|
### temporarily back up the current configuration files from %s to %s: %s
|
NOTICE_CONFIG_RESTORE_RESTORED_OLD_CONFIG_408=\u51fa\u73b0\u9519\u8bef\uff0c\u5bfc\u81f4\u65e0\u6cd5\u6b63\u786e\u6062\u590d\u914d\u7f6e\u5907\u4efd\u3002\u4e0d\u8fc7\uff0c\u5df2\u4fdd\u7559\u5728\u6062\u590d\u8fc7\u7a0b\u5f00\u59cb\u4e4b\u524d\u4f4d\u4e8e\u9002\u5f53\u4f4d\u7f6e\u7684\u539f\u59cb\u914d\u7f6e\u6587\u4ef6\uff0c\u8fd9\u4e9b\u6587\u4ef6\u73b0\u5728\u4f4d\u4e8e\u5176\u539f\u59cb\u4f4d\u7f6e %s \u4e2d
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_RESTORE_OLD_CONFIG_409=An error occurred \
|
### that prevented the configuration backup from being properly restored. The \
|
### original configuration files that were in place before the start of the \
|
### restore process have been preserved and are contained in the %s directory
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CREATE_CONFIG_DIRECTORY_410=Unable to \
|
### restore configuration backup %s because an error occurred while attempting to \
|
### create a new empty directory %s into which the files should be restored: %s
|
###SEVERE_ERR_CONFIG_RESTORE_OLD_CONFIG_SAVED_411=An error occurred that \
|
### prevented the configuration backup from being properly restored. The \
|
### original configuration files that were in place before the start of the \
|
### restore process have been preserved in the %s directory
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_ZIP_ENTRY_412=Unable to restore or \
|
### verify configuration backup %s because an error occurred while trying to read \
|
### the next entry from the archive file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CREATE_FILE_413=Unable to restore \
|
### configuration backup %s because an error occurred while trying to recreate \
|
### file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_PROCESS_ARCHIVE_FILE_414=Unable to restore \
|
### or verify configuration backup %s because an error occurred while processing \
|
### archived file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_ERROR_ON_ZIP_STREAM_CLOSE_415=Unable to restore or \
|
### verify configuration backup %s because an unexpected error occurred while \
|
### trying to close the archive file %s: %s
|
NOTICE_CONFIG_RESTORE_UNSIGNED_HASH_VALID_416=\u901a\u8fc7\u5907\u4efd\u5f52\u6863\u6587\u4ef6\u8ba1\u7b97\u7684\u6d88\u606f\u6458\u8981\u4e0e\u968f\u5907\u4efd\u4fe1\u606f\u4e00\u8d77\u5b58\u50a8\u7684\u6458\u8981\u76f8\u5339\u914d
|
###SEVERE_ERR_CONFIG_RESTORE_UNSIGNED_HASH_INVALID_417=Unable to restore or \
|
### verify configuration backup %s because the message digest calculated from the \
|
### backup archive does not match the digest stored with the backup information
|
NOTICE_CONFIG_RESTORE_SIGNED_HASH_VALID_418=\u901a\u8fc7\u5907\u4efd\u5f52\u6863\u6587\u4ef6\u8ba1\u7b97\u7684\u7b7e\u540d\u6458\u8981\u4e0e\u968f\u5907\u4efd\u4fe1\u606f\u4e00\u8d77\u5b58\u50a8\u7684\u7b7e\u540d\u76f8\u5339\u914d
|
###SEVERE_ERR_CONFIG_RESTORE_SIGNED_HASH_INVALID_419=Unable to restore or verify \
|
### configuration backup %s because the signed digest calculated from the backup \
|
### archive does not match the signature stored with the backup information
|
NOTICE_CONFIG_RESTORE_VERIFY_SUCCESSFUL_420=\u5bf9\u76ee\u5f55 %2$s \u4e2d\u7684\u914d\u7f6e\u5907\u4efd %1$s \u6267\u884c\u7684\u6240\u6709\u6d4b\u8bd5\u8868\u660e\u5f52\u6863\u6587\u4ef6\u4f3c\u4e4e\u6709\u6548
|
NOTICE_CONFIG_RESTORE_SUCCESSFUL_421=\u5df2\u6210\u529f\u4ece\u76ee\u5f55 %2$s \u4e2d\u7684\u5f52\u6863\u6587\u4ef6\u6062\u590d\u914d\u7f6e\u5907\u4efd %1$s
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCK_422=The Directory Server \
|
### was unable to acquire a shared lock for backend %s: %s. This generally \
|
### means that the backend is in use by a process that requires an exclusive lock \
|
### (e.g., importing from LDIF or restoring a backup). This backend will be \
|
### disabled
|
###SEVERE_WARN_CONFIG_BACKEND_CANNOT_RELEASE_SHARED_LOCK_423=An error occurred \
|
### while attempting to release a shared lock for backend %s: %s. This may \
|
### interfere with operations that require exclusive access, including LDIF \
|
### import and restoring a backup
|
INFO_CONFIG_FILE_HEADER_424=\u8be5\u6587\u4ef6\u5305\u542b\u4e3b\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u3002\u5f53\u670d\u52a1\u5668\u8054\u673a\u65f6\uff0c\u4e0d\u80fd\u76f4\u63a5\u7f16\u8f91\u8be5\u6587\u4ef6\u3002\u53ea\u5e94\u4f7f\u7528\u968f\u76ee\u5f55\u670d\u52a1\u5668\u63d0\u4f9b\u7684\u7ba1\u7406\u5b9e\u7528\u7a0b\u5e8f\u6765\u7ba1\u7406\u670d\u52a1\u5668\u914d\u7f6e
|
INFO_CONFIG_CORE_DESCRIPTION_ADD_MISSING_RDN_ATTRS_425=\u6307\u793a\u5728\u6dfb\u52a0\u6761\u76ee\u65f6\uff0c\u76ee\u5f55\u670d\u52a1\u5668\u662f\u5426\u5e94\u81ea\u52a8\u5411\u5176\u4e2d\u6dfb\u52a0\u7f3a\u5c11\u7684 RDN \u5c5e\u6027\u3002\u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0c\u5982\u679c\u6240\u6dfb\u52a0\u6761\u76ee\u7684\u5c5e\u6027\u5217\u8868\u4e2d\u4e0d\u5305\u542b RDN \u5c5e\u6027\u503c\uff0c\u5219\u4f1a\u62d2\u7edd\u8fd9\u4e9b\u6761\u76ee\uff0c\u56e0\u4e3a\u5b83\u4eec\u8fdd\u53cd\u4e86 LDAP \u89c4\u8303\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ADD_MISSING_RDN_ATTRS_426=Configuration entry \
|
### %s has an invalid value for configuration attribute \
|
### ds-cfg-add-missing-rdn-attributes (it should be a Boolean value of true or \
|
### false): %s
|
INFO_CONFIG_CORE_DESCRIPTION_SERVER_ERROR_RESULT_CODE_427=\u5e94\u8be5\u7528\u4e8e\u54cd\u5e94\uff08\u64cd\u4f5c\u56e0\u5185\u90e8\u670d\u52a1\u5668\u9519\u8bef\u800c\u5931\u8d25\u65f6\u53d1\u51fa\u6b64\u7c7b\u54cd\u5e94\uff09\u7684\u7ed3\u679c\u4ee3\u7801\u3002\u8be5\u503c\u5e94\u8be5\u4e3a\u4e0e\u76f8\u5e94 LDAP \u7ed3\u679c\u4ee3\u7801\u7b49\u6548\u7684\u6574\u6570\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SERVER_ERROR_RESULT_CODE_428=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-server-error-result-code (it should be an integer value greater than \
|
### or equal to 1): %s
|
###FATAL_ERR_CONFIG_IDMAPPER_CANNOT_GET_BASE_429=An error occurred while \
|
### attempting to retrieve the identity mapper base entry cn=Identity \
|
### Mappers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_IDMAPPER_BASE_DOES_NOT_EXIST_430=The identity mapper \
|
### configuration base cn=Identity Mappers,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_IDMAPPER_ENTRY_UNACCEPTABLE_431=Configuration entry %s does \
|
### not contain a valid identity mapper configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_IDMAPPER_CANNOT_CREATE_MAPPER_432=An error occurred while \
|
### attempting to create a Directory Server identity mapper from the information \
|
### in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_OBJECTCLASS_433=Configuration entry %s \
|
### does not contain the ds-cfg-identity-mapper objectclass, which is required \
|
### for identity mapper definitions
|
INFO_CONFIG_IDMAPPER_DESCRIPTION_CLASS_NAME_434=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u8eab\u4efd\u6620\u5c04\u5668\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u8eab\u4efd\u6620\u5c04\u5668\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u6620\u5c04\u5668\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_CLASS_NAME_435=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class name \
|
### for the associated identity mapper
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_NAME_436=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_437=Class %s specified in \
|
### configuration entry %s does not contain a valid identity mapper \
|
### implementation: %s
|
INFO_CONFIG_IDMAPPER_DESCRIPTION_ENABLED_438=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u8eab\u4efd\u6620\u5c04\u5668\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_ENABLED_ATTR_439=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the identity mapper \
|
### should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_ENABLED_VALUE_440=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_IDMAPPER_CLASS_ACTION_REQUIRED_441=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u8eab\u4efd\u6620\u5c04\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8eab\u4efd\u6620\u5c04\u5668\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED_442=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8eab\u4efd\u6620\u5c04\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_IDMAPPER_EXISTS_443=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u8eab\u4efd\u6620\u5c04\u5668\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u8eab\u4efd\u6620\u5c04\u5668
|
###SEVERE_ERR_CONFIG_IDMAPPER_UNACCEPTABLE_CONFIG_444=The configuration for the \
|
### identity mapper defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_PROXY_MAPPER_DN_445=\u8eab\u4efd\u6620\u5c04\u5668\u914d\u7f6e\u6761\u76ee\u7684 DN\uff0c\u76ee\u5f55\u670d\u52a1\u5668\u5c06\u8be5\u8eab\u4efd\u6620\u5c04\u5668\u4e0e\u4ee3\u7406\u6388\u6743 V2 \u63a7\u5236\u7ed3\u5408\u4f7f\u7528\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_PROXY_MAPPER_DN_446=Configuration entry %s has \
|
### an invalid value for configuration attribute \
|
### ds-cfg-proxied-authorization-identity-mapper (it should be the DN of a \
|
### valid identity mapper configuration entry): %s
|
###SEVERE_ERR_CONFIG_CORE_NO_PROXY_MAPPER_FOR_DN_447=The proxied authorization \
|
### identity mapper DN %s specified in configuration entry %s does not refer to a \
|
### valid identity mapper configuration entry
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_PROXY_MAPPER_DN_448=The Directory Server does \
|
### not have any identity mapper configured for use in conjunction with proxied \
|
### authorization V2 operations. The Directory Server will not be able to \
|
### process requests containing the proxied authorization control with a \
|
### username-based authorization ID
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_PROXY_MAPPER_DN_449=The configured proxied \
|
### authorization identity mapper DN %s does not refer to an active identity \
|
### mapper. The Directory Server will not be able to process requests containing \
|
### the proxied authorization control with a username-based authorization ID
|
INFO_CONFIG_CORE_DESCRIPTION_SIZE_LIMIT_450=\u5728\u5904\u7406\u641c\u7d22\u64cd\u4f5c\u65f6\u5e94\u4e3a\u5ba2\u6237\u7aef\u8fd4\u56de\u7684\u9ed8\u8ba4\u6700\u5927\u6761\u76ee\u6570\u3002\u53ef\u901a\u8fc7\u5728\u7528\u6237\u6761\u76ee\u4e2d\u5305\u542b ds-rlim-size-limit \u64cd\u4f5c\u5c5e\u6027\uff0c\u9010\u4e00\u4e3a\u7528\u6237\u8986\u76d6\u8be5\u6570\u503c\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SIZE_LIMIT_451=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-size-limit (It should be a \
|
### positive integer value specifying the size limit to use, or a value of 0 or \
|
### -1 to indicate that no limit should be enforced): %s
|
###FATAL_ERR_CONFIG_SYNCH_CANNOT_GET_CONFIG_BASE_452=An error occurred while \
|
### attempting to retrieve the Directory Server synchronization provider \
|
### configuration base entry cn=Synchronization Providers,cn=config: %s
|
###FATAL_ERR_CONFIG_SYNCH_BASE_DOES_NOT_EXIST_453=The Directory Server \
|
### synchronization provider base entry cn=Synchronization Providers,cn=config \
|
### does not exist. This entry must be present in the Directory Server \
|
### configuration
|
###FATAL_ERR_CONFIG_SYNCH_ENTRY_DOES_NOT_HAVE_PROVIDER_CONFIG_454=Configuration \
|
### entry %s exists below the Directory Server synchronization provider root but \
|
### does not contain attribute ds-cfg-synchronization-provider which must be \
|
### present in all synchronization provider configuration entries
|
###FATAL_ERR_CONFIG_SYNCH_CANNOT_CHECK_FOR_PROVIDER_CONFIG_OC_455=An error \
|
### occurred while attempting to determine whether configuration entry %s was a \
|
### valid Directory Server synchronization provider: %s
|
INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_ENABLED_456=\u6307\u793a\u662f\u5426\u542f\u7528\u4e86\u5173\u8054\u7684\u76ee\u5f55\u670d\u52a1\u5668\u540c\u6b65\u63d0\u4f9b\u7a0b\u5e8f\uff0c\u4ee5\u53ca\u670d\u52a1\u5668\u662f\u5426\u5e94\u4f7f\u7528\u8be5\u63d0\u4f9b\u7a0b\u5e8f\u3002\u6240\u6709\u540c\u6b65\u63d0\u4f9b\u7a0b\u5e8f\u6761\u76ee\u4e2d\u90fd\u5fc5\u987b\u5b58\u5728\u8be5\u5c5e\u6027\uff0c\u5e76\u4e14\u4e0d\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8fd0\u884c\u65f6\u66f4\u6539\u8be5\u5c5e\u6027
|
###FATAL_ERR_CONFIG_SYNCH_PROVIDER_NO_ENABLED_ATTR_457=Synchronization provider \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-enabled which indicates whether the \
|
### synchronization provider is enabled for use
|
###SEVERE_WARN_CONFIG_SYNCH_PROVIDER_DISABLED_458=The Directory Server \
|
### synchronization provider defined in configuration entry %s is disabled. This \
|
### provider will not be used
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_ENABLED_STATE_459=An error \
|
### occurred while attempting to determine whether the Directory Server \
|
### synchronization provider defined in configuration entry %s should be enabled: \
|
### %s
|
INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_CLASS_460=\u5c06\u4e3a\u76ee\u5f55\u670d\u52a1\u5668\u540c\u6b65\u63d0\u4f9b\u7a0b\u5e8f\u63d0\u4f9b\u903b\u8f91\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u6240\u6709\u540c\u6b65\u63d0\u4f9b\u7a0b\u5e8f\u6761\u76ee\u4e2d\u90fd\u5fc5\u987b\u5b58\u5728\u8be5\u5c5e\u6027\uff0c\u5e76\u4e14\u4e0d\u53ef\u4ee5\u5728\u76ee\u5f55\u670d\u52a1\u5668\u8fd0\u884c\u65f6\u66f4\u6539\u8be5\u5c5e\u6027
|
###FATAL_ERR_CONFIG_SYNCH_NO_CLASS_ATTR_461=Synchronization provider \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-java-class which specifies the name of the class \
|
### that implements the synchronization provider logic
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_CLASS_462=An error occurred while \
|
### attempting to determine the name of the class used to provide the Directory \
|
### Server synchronization provider logic from configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_LOAD_PROVIDER_CLASS_463=An error occurred \
|
### while attempting to load class %s referenced in synchronization provider \
|
### configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDER_464=An error occurred \
|
### while attempting to instantiate class %s referenced in synchronization \
|
### provider configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDER_465=An error occurred \
|
### while attempting to initialize the Directory Server synchronization provider \
|
### referenced in configuration entry %s: %s
|
INFO_CONFIG_SYNCH_PROVIDER_HAS_BEEN_DISABLED_466=\u5f53\u524d\u542f\u7528\u4e86\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u540c\u6b65\u63d0\u4f9b\u7a0b\u5e8f\uff0c\u4f46\u5df2\u66f4\u6539\u4e86\u914d\u7f6e\uff0c\u56e0\u6b64\uff0c\u5e94\u7981\u7528\u8be5\u63d0\u4f9b\u7a0b\u5e8f\u3002\u5728\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u6b64\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###FATAL_ERR_CONFIG_SYNCH_PROVIDER_CLASS_CHANGED_467=The Java class providing \
|
### the logic for the synchronization provider defined in configuration entry %s \
|
### has changed from %s to %s. This will not take effect until the Directory \
|
### Server is restarted
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_WRITABILITY_468=\u8be5\u540e\u7aef\u7684\u53ef\u5199\u5165\u6a21\u5f0f\u3002\u8be5\u503c\u53ef\u4ee5\u4e3a "enabled"\uff08\u5141\u8bb8\u6240\u6709\u5199\u5165\u64cd\u4f5c\uff09\u3001"disabled"\uff08\u62d2\u7edd\u6240\u6709\u5199\u5165\u64cd\u4f5c\uff09\u6216 "internal-only"\uff08\u4ec5\u5141\u8bb8\u5185\u90e8\u5199\u5165\u64cd\u4f5c\u548c\u540c\u6b65\u66f4\u65b0\uff09\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_BACKEND_NO_WRITABILITY_MODE_469=The backend defined in \
|
### configuration entry %s does not have a value for configuration attribute \
|
### ds-cfg-writability-mode which indicates the writability mode for that \
|
### backend. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_INVALID_WRITABILITY_MODE_470=The backend defined in \
|
### configuration entry %s has an invalid writability mode of %s. The backend \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_WRITABILITY_471=An unexpected \
|
### error occurred while attempting to determine the writability mode for the \
|
### backend defined in configuration entry %s: %s. The backend will be disabled
|
INFO_CONFIG_CORE_DESCRIPTION_WRITABILITY_MODE_472=\u76ee\u5f55\u670d\u52a1\u5668\u7684\u53ef\u5199\u5165\u6a21\u5f0f\u3002\u8be5\u503c\u53ef\u4ee5\u4e3a "enabled"\u3001"disabled" \u6216 "internal-only" \u4e4b\u4e00\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_WRITABILITY_MODE_473=Configuration entry %s \
|
### has an invalid value for configuration attribute ds-cfg-writability-mode (the \
|
### value should be one of "enabled", "disabled", or "internal-only"): %s
|
INFO_CONFIG_CORE_DESCRIPTION_BIND_WITH_DN_REQUIRES_PW_474=\u6307\u793a\u5305\u542b DN \u7684\u7b80\u5355\u7ed1\u5b9a\u662f\u5426\u8fd8\u9700\u8981\u5305\u542b\u5bc6\u7801\u3002\u5982\u679c\u7981\u7528\u8be5\u9009\u9879\uff0c\u5219\u4f1a\u59cb\u7ec8\u5c06\u6ca1\u6709\u5bc6\u7801\u7684\u7ed1\u5b9a\u89c6\u4e3a\u533f\u540d\u7ed1\u5b9a\uff08\u5373\u4f7f\u5b83\u4eec\u5305\u542b\u7ed1\u5b9a DN\uff09\uff0c\u5728\u67d0\u4e9b\u7c7b\u578b\u7684\u5e94\u7528\u7a0b\u5e8f\u4e2d\u8fd9\u53ef\u80fd\u4f1a\u4ea7\u751f\u5b89\u5168\u6f0f\u6d1e\u3002\u5982\u679c\u542f\u7528\u8be5\u9009\u9879\uff0c\u5219\u4f1a\u62d2\u7edd\u5305\u542b DN \u4f46\u4e0d\u5305\u542b\u5bc6\u7801\u7684\u4efb\u4f55\u7b80\u5355\u7ed1\u5b9a\u8bf7\u6c42\uff0c\u800c\u4e0d\u662f\u9ed8\u8ba4\u8fdb\u884c\u533f\u540d\u9a8c\u8bc1\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_BIND_WITH_DN_REQUIRES_PW_475=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-bind-with-dn-requires-password (the value should be either "TRUE" or \
|
### "FALSE"): %s
|
###FATAL_ERR_CONFIG_PWVALIDATOR_CANNOT_GET_BASE_476=An error occurred while \
|
### attempting to retrieve the password validator base entry cn=Password \
|
### Validators,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWVALIDATOR_BASE_DOES_NOT_EXIST_477=The password validator \
|
### configuration base cn=Password Validators,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_ENTRY_UNACCEPTABLE_478=Configuration entry %s \
|
### does not contain a valid password validator configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_CANNOT_CREATE_VALIDATOR_479=An error occurred \
|
### while attempting to create a Directory Server password validator from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_OBJECTCLASS_480=Configuration entry %s \
|
### does not contain the ds-cfg-password-validator objectclass, which is required \
|
### for password validator definitions
|
INFO_CONFIG_PWVALIDATOR_DESCRIPTION_CLASS_NAME_481=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u9a8c\u8bc1\u5668\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u9a8c\u8bc1\u5668\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u9a8c\u8bc1\u5668\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_NO_CLASS_NAME_482=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated password validator
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_NAME_483=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_484=Class %s specified in \
|
### configuration entry %s does not contain a valid password validator \
|
### implementation: %s
|
INFO_CONFIG_PWVALIDATOR_DESCRIPTION_ENABLED_485=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u9a8c\u8bc1\u5668\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_NO_ENABLED_ATTR_486=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### validator should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_ENABLED_VALUE_487=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_PWVALIDATOR_CLASS_ACTION_REQUIRED_488=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u5bc6\u7801\u9a8c\u8bc1\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u9a8c\u8bc1\u5668\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED_489=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u9a8c\u8bc1\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_PWVALIDATOR_EXISTS_490=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u5bc6\u7801\u9a8c\u8bc1\u5668\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u9a8c\u8bc1\u5668
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_UNACCEPTABLE_CONFIG_491=The configuration for \
|
### the password validator defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_PWGENERATOR_CANNOT_GET_BASE_492=An error occurred while \
|
### attempting to retrieve the password generator base entry cn=Password \
|
### Generators,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWGENERATOR_BASE_DOES_NOT_EXIST_493=The password generator \
|
### configuration base cn=Password Generators,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWGENERATOR_ENTRY_UNACCEPTABLE_494=Configuration entry %s \
|
### does not contain a valid password generator configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWGENERATOR_CANNOT_CREATE_GENERATOR_495=An error occurred \
|
### while attempting to create a Directory Server password generator from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_OBJECTCLASS_496=Configuration entry %s \
|
### does not contain the ds-cfg-password-generator objectclass, which is required \
|
### for password generator definitions
|
INFO_CONFIG_PWGENERATOR_DESCRIPTION_CLASS_NAME_497=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u751f\u6210\u5668\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u751f\u6210\u5668\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u751f\u6210\u5668\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWGENERATOR_NO_CLASS_NAME_498=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated password generator
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_NAME_499=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_500=Class %s specified in \
|
### configuration entry %s does not contain a valid password generator \
|
### implementation: %s
|
INFO_CONFIG_PWGENERATOR_DESCRIPTION_ENABLED_501=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u5bc6\u7801\u751f\u6210\u5668\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_PWGENERATOR_NO_ENABLED_ATTR_502=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### generator should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_ENABLED_VALUE_503=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_PWGENERATOR_CLASS_ACTION_REQUIRED_504=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u5bc6\u7801\u751f\u6210\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u751f\u6210\u5668\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED_505=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u751f\u6210\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_PWGENERATOR_EXISTS_506=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u5bc6\u7801\u751f\u6210\u5668\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u751f\u6210\u5668
|
###SEVERE_ERR_CONFIG_PWGENERATOR_UNACCEPTABLE_CONFIG_507=The configuration for \
|
### the password generator defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_DEFAULT_PWPOLICY_DN_508=\u4e3a\u76ee\u5f55\u670d\u52a1\u5668\u5b9a\u4e49\u9ed8\u8ba4\u5bc6\u7801\u7b56\u7565\u7684\u914d\u7f6e\u6761\u76ee\u7684 DN\uff0c\u5b83\u5c06\u5e94\u7528\u4e8e\u6240\u6709\u672a\u5b9a\u4e49\u81ea\u5b9a\u4e49\u5bc6\u7801\u7b56\u7565\u7684\u7528\u6237\u3002\u8be5\u6761\u76ee\u5fc5\u987b\u5b58\u5728\uff0c\u5e76\u4e14\u5fc5\u987b\u6307\u5b9a\u6709\u6548\u7684\u5bc6\u7801\u7b56\u7565\u914d\u7f6e\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_NO_DEFAULT_PWPOLICY_509=No default password policy was \
|
### configured for the Directory Server. This must be specified by the \
|
### ds-cfg-default-password-policy attribute in configuration entry %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_DEFAULT_PWPOLICY_DN_510=Configuration entry %s \
|
### has an invalid value for configuration attribute \
|
### ds-cfg-default-password-policy (the value should a DN specifying the default \
|
### password policy configuration entry): %s
|
###SEVERE_ERR_CONFIG_CORE_NO_SUCH_PWPOLICY_511=The value %s for configuration \
|
### attribute ds-cfg-default-password-policy does not refer to a valid password \
|
### policy configuration entry
|
###FATAL_ERR_CONFIG_PWPOLICY_CANNOT_GET_BASE_512=An error occurred while \
|
### attempting to retrieve the password policy base entry cn=Password \
|
### Policies,cn=config from the Directory Server configuration: %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_BASE_DOES_NOT_EXIST_513=The password policy \
|
### configuration base cn=Password Policies,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWPOLICY_NO_POLICIES_514=No password policies have been \
|
### defined below the cn=Password Policies,cn=config entry in the Directory \
|
### Server configuration. At least one password policy configuration must be \
|
### defined
|
###SEVERE_ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIG_515=The password policy \
|
### defined in configuration entry %s is invalid: %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_MISSING_DEFAULT_POLICY_516=The Directory Server \
|
### default password policy is defined as %s, but that entry does not exist or is \
|
### not below the password policy configuration base cn=Password \
|
### Policies,cn=config
|
###SEVERE_WARN_CONFIG_PWPOLICY_CANNOT_DELETE_DEFAULT_POLICY_517=The specified \
|
### entry %s is currently defined as the configuration entry for the default \
|
### password policy. The default password policy configuration entry may not be \
|
### removed
|
INFO_CONFIG_PWPOLICY_REMOVED_POLICY_518=\u5df2\u4ece\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u5220\u9664\u5bc6\u7801\u7b56\u7565\u6761\u76ee %s\u3002\u5c06\u4e0d\u518d\u5141\u8bb8\u9a8c\u8bc1\u4efb\u4f55\u663e\u5f0f\u5f15\u7528\u8be5\u5bc6\u7801\u7b56\u7565\u7684\u7528\u6237\u6761\u76ee
|
###FATAL_ERR_CONFIG_AUTHZ_CANNOT_GET_ENTRY_519=An error occurred while \
|
### attempting to retrieve the Directory Server access control configuration \
|
### entry cn=Access Control Handler,cn=config: %s
|
###FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_EXIST_520=The Directory Server access \
|
### control configuration entry cn=Access Control Handler,cn=config does not \
|
### exist. This entry must be present in the Directory Server configuration
|
###FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_HAVE_OBJECT_CLASS_521=The Directory \
|
### Server access control configuration entry cn=Access Control Handler,cn=config \
|
### does not have the correct object class. This entry must have the object \
|
### class ds-cfg-access-control-handler in order to be valid
|
INFO_CONFIG_AUTHZ_DESCRIPTION_ENABLED_523=\u6307\u793a\u662f\u5426\u542f\u7528\u4e86\u8bbf\u95ee\u63a7\u5236\u4ee5\u53ca\u670d\u52a1\u5668\u662f\u5426\u5e94\u4f7f\u7528\u8bbf\u95ee\u63a7\u5236\u3002\u8be5\u5c5e\u6027\u662f\u5fc5\u9700\u5c5e\u6027
|
###FATAL_ERR_CONFIG_AUTHZ_NO_ENABLED_ATTR_524=The access control configuration \
|
### entry %s does not contain attribute ds-cfg-enabled which \
|
### indicates whether the access control is enabled for use
|
###SEVERE_WARN_CONFIG_AUTHZ_DISABLED_525=Access control has been disabled
|
NOTICE_CONFIG_AUTHZ_ENABLED_526=\u8bbf\u95ee\u63a7\u5236\u5df2\u542f\u7528\u5e76\u5c06\u4f7f\u7528 %s \u5b9e\u73b0
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_ENABLED_STATE_527=An error \
|
### occurred while attempting to determine whether the Directory Server access \
|
### control as defined in configuration entry %s should be enabled: %s
|
INFO_CONFIG_AUTHZ_DESCRIPTION_CLASS_528=\u4e3a\u76ee\u5f55\u670d\u52a1\u5668\u63d0\u4f9b\u8bbf\u95ee\u63a7\u5236\u5b9e\u73b0\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u8be5\u5c5e\u6027\u662f\u5fc5\u9700\u5c5e\u6027
|
###FATAL_ERR_CONFIG_AUTHZ_NO_CLASS_ATTR_529=The access control configuration \
|
### entry %s does not contain attribute ds-cfg-java-class which specifies \
|
### the name of the Java class providing the access control implementation for \
|
### the Directory Server
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_CLASS_530=An error occurred while \
|
### attempting to determine the name of the class used to provide the Directory \
|
### Server access control implementation from configuration entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_LOAD_CLASS_531=An error occurred while \
|
### attempting to load class %s referenced in the access control configuration \
|
### entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_BAD_CLASS_532=The access control implementation class \
|
### %s referenced in the access control configuration entry %s does not implement \
|
### the %s interface: %s
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLER_533=An error occurred \
|
### while attempting to instantiate class %s referenced in the access control \
|
### configuration entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_ERROR_INITIALIZING_HANDLER_534=An error occurred while \
|
### attempting to initialize the Directory Server access control implementation \
|
### referenced in configuration entry %s: %s
|
###FATAL_ERR_CONFIG_ROOTDN_CANNOT_GET_BASE_535=An error occurred while \
|
### attempting to retrieve the root DN base entry cn=Root DNs,cn=config from the \
|
### Directory Server configuration: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_BASE_DOES_NOT_EXIST_536=The password policy \
|
### configuration base cn=Root DNs,cn=config does not exist in the Directory \
|
### Server configuration. This entry must be present for the server to function \
|
### properly
|
###SEVERE_ERR_CONFIG_ROOTDN_ENTRY_UNACCEPTABLE_537=Configuration entry %s does \
|
### not contain a valid root DN configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_CREATE_538=An error occurred while attempting \
|
### to create a Directory Server root DN from the information in configuration \
|
### entry %s: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_INVALID_OBJECTCLASS_539=Configuration entry %s does \
|
### not contain the ds-cfg-root-dn-user objectclass, which is required for Directory \
|
### Server root DN definitions
|
INFO_CONFIG_ROOTDN_DESCRIPTION_ALTERNATE_BIND_DN_540=\u9664\u4e86\u6839 DN \u914d\u7f6e\u6761\u76ee\u7684\u5b9e\u9645 DN \u4ee5\u5916\uff0c\u6307\u5b9a\u4e00\u4e2a\u6216\u591a\u4e2a\u5907\u7528\u7ed1\u5b9a DN\uff0c\u53ef\u4ee5\u5c06\u8fd9\u4e9b DN \u4f5c\u4e3a\u5173\u8054\u7684\u6839 DN \u8fdb\u884c\u9a8c\u8bc1\u3002\u5907\u7528\u7ed1\u5b9a DN \u4e0d\u80fd\u4e0e\u76ee\u5f55\u4e2d\u4efb\u4f55\u5176\u4ed6\u6761\u76ee\u7684 DN \u53d1\u751f\u51b2\u7a81\uff0c\u4e5f\u4e0d\u80fd\u4e0e\u4e3a\u5176\u4ed6\u6839 DN \u914d\u7f6e\u7684\u5907\u7528\u7ed1\u5b9a DN \u53d1\u751f\u51b2\u7a81\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_ROOTDN_CONFLICTING_MAPPING_541=Unable to register "%s" as \
|
### an alternate bind DN for user "%s" because it is already registered as an \
|
### alternate bind DN for root user "%s"
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_PARSE_ALTERNATE_BIND_DNS_542=An error \
|
### occurred while trying to parse the set of alternate bind DNs for root user \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_REGISTER_ALTERNATE_BIND_DN_543=An error \
|
### occurred while trying to register"%s" as an alternate bind DN for root user \
|
### "%s": %s
|
###SEVERE_ERR_CONFIG_ROOTDN_EXISTS_544=Unable to add root DN entry %s because \
|
### another root user is already registered with that DN
|
###FATAL_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_GET_BASE_545=An error occurred while \
|
### attempting to retrieve the account status notification handler base entry \
|
### cn=Account Status Notification Handlers,cn=config from the Directory Server \
|
### configuration: %s
|
###SEVERE_WARN_CONFIG_ACCTNOTHANDLER_BASE_DOES_NOT_EXIST_546=The account status \
|
### notification handler configuration base cn=Account Status Notification \
|
### Handlers,cn=config does not exist in the Directory Server configuration. \
|
### This entry must be present for the server to function properly
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_ENTRY_UNACCEPTABLE_547=Configuration entry \
|
### %s does not contain a valid account status notification handler \
|
### configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_CREATE_HANDLER_548=An error occurred \
|
### while attempting to create a Directory Server account status notification \
|
### handler from the information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_OBJECTCLASS_549=Configuration entry \
|
### %s does not contain the ds-cfg-account-status-notification-handler \
|
### objectclass, which is required for account status notification handler \
|
### definitions
|
INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_CLASS_NAME_550=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u5904\u7406\u7a0b\u5e8f\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_CLASS_NAME_551=Configuration entry %s \
|
### does not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the \
|
### fully-qualified class name for the associated account status notification \
|
### handler
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_NAME_552=Configuration entry \
|
### %s has an invalid value for attribute \
|
### ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_553=Class %s specified in \
|
### configuration entry %s does not contain a valid account status notification \
|
### handler implementation: %s
|
INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_ENABLED_554=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_ENABLED_ATTR_555=Configuration entry %s \
|
### does not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether \
|
### the account status notification handler should be enabled for use in the \
|
### Directory Server
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_ENABLED_VALUE_556=Configuration \
|
### entry %s has an invalid value for attribute \
|
### ds-cfg-enabled: %s
|
INFO_CONFIG_ACCTNOTHANDLER_CLASS_ACTION_REQUIRED_557=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED_558=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_EXISTS_559=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u901a\u77e5\u5904\u7406\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_UNACCEPTABLE_CONFIG_560=The configuration \
|
### for the account status notification handler defined in configuration entry %s \
|
### was not acceptable according to its internal validation. However, no \
|
### specific information is available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_LOOKTHROUGH_LIMIT_561=\u5728\u5904\u7406\u641c\u7d22\u64cd\u4f5c\u65f6\uff0c\u68c0\u67e5\u7684\u9ed8\u8ba4\u6700\u5927\u5019\u9009\u6761\u76ee\u6570\uff08\u4ee5\u5bfb\u627e\u5339\u914d\u9879\uff09\u3002\u53ef\u901a\u8fc7\u5728\u7528\u6237\u6761\u76ee\u4e2d\u5305\u542b ds-rlim-lookthrough-limit \u64cd\u4f5c\u5c5e\u6027\uff0c\u9010\u4e00\u4e3a\u7528\u6237\u8986\u76d6\u8be5\u6570\u503c\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_LOOKTHROUGH_LIMIT_562=Configuration entry %s \
|
### has an invalid value for configuration attribute ds-cfg-lookthrough-limit (It \
|
### should be a positive integer value specifying the lookthrough limit to use, \
|
### or a value of 0 or -1 to indicate that no limit should be enforced): %s
|
###FATAL_ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGES_563=An error occurred while \
|
### attempting to apply the changes contained in file %s to the server \
|
### configuration at startup: %s
|
###FATAL_ERR_CONFIG_ERROR_APPLYING_STARTUP_CHANGE_564=Unable to apply a change \
|
### at server startup: %s
|
###FATAL_ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE_565=One or more errors occurred \
|
### while applying changes on server startup
|
INFO_CONFIG_DESCRIPTION_BACKEND_MODE_566=\u7528\u4e8e\u5305\u542b\u540e\u7aef\u6570\u636e\u5e93\u6587\u4ef6\u7684\u76ee\u5f55\u7684\u6743\u9650
|
###SEVERE_ERR_CONFIG_BACKEND_MODE_INVALID_567=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It \
|
### should be an UNIX permission mode in three-digit octal notation.)
|
###SEVERE_ERR_CONFIG_BACKEND_INSANE_MODE_568=Invalid UNIX file permissions %s \
|
### does not allow read and write access to the backend database directory by \
|
### the backend
|
INFO_CONFIG_CORE_DESCRIPTION_TIME_LIMIT_569=\u5728\u5904\u7406\u641c\u7d22\u64cd\u4f5c\u65f6\u5e94\u5141\u8bb8\u7684\u9ed8\u8ba4\u6700\u5927\u65f6\u95f4\u957f\u5ea6\u3002\u53ef\u901a\u8fc7\u5728\u7528\u6237\u6761\u76ee\u4e2d\u5305\u542b ds-rlim-time-limit \u64cd\u4f5c\u5c5e\u6027\uff0c\u9010\u4e00\u4e3a\u7528\u6237\u8986\u76d6\u8be5\u6570\u503c\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_INVALID_TIME_LIMIT_570=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-time-limit (it should be an \
|
### integer value followed by a space and a time unit of seconds, minutes, hours, \
|
### days, or weeks): %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_NO_DEFAULT_POLICY_571=No default password policy \
|
### is configured for the Directory Server. The default password policy must be \
|
### specified by the ds-cfg-default-password-policy attribute in the cn=config \
|
### entry
|
###SEVERE_WARN_CONFIG_BACKEND_CANNOT_REGISTER_BACKEND_572=An error occurred \
|
### while attempting to register backend %s with the Directory Server: %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_NO_REASON_573=An error \
|
### occurred while trying to create the configuration archive directory %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_574=An error occurred while \
|
### trying to create the configuration archive directory %s: %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVE_575=An error occurred \
|
### while trying to write the current configuration to the configuration archive: \
|
### %s
|
INFO_CONFIG_CORE_DESCRIPTION_REJECT_UNAUTHENTICATED_REQUESTS_576=\u6307\u793a\u76ee\u5f55\u670d\u52a1\u5668\u662f\u5426\u5e94\u62d2\u7edd\u6765\u81ea\u672a\u7ecf\u9a8c\u8bc1\u7684\u5ba2\u6237\u7aef\u7684\u8bf7\u6c42\u3002\u5982\u679c\u5c06\u6b64\u9009\u9879\u8bbe\u7f6e\u4e3a\u201c\u771f\u201d\uff0c\u5219\u4ec5\u5141\u8bb8\u672a\u7ecf\u9a8c\u8bc1\u7684\u5ba2\u6237\u7aef\u53d1\u9001\u7ed1\u5b9a\u548c StartTLS \u8bf7\u6c42\u3002\u5bf9\u6b64\u914d\u7f6e\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_CORE_REJECT_UNAUTHENTICATED_REQUESTS_INVALID_577=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-reject-unauthenticated-requests(the value should be either true or \
|
### false)
|
###FATAL_ERR_CONFIG_GROUP_CANNOT_GET_BASE_578=An error occurred while attempting \
|
### to retrieve the group implementation base entry cn=Group \
|
### Implementations,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_GROUP_BASE_DOES_NOT_EXIST_579=The group implementation \
|
### configuration base cn=Group Implementations,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_GROUP_ENTRY_UNACCEPTABLE_580=Configuration entry %s does \
|
### not contain a valid group implementation configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_GROUP_CANNOT_CREATE_IMPLEMENTATION_581=An error occurred \
|
### while attempting to create a Directory Server group implementation from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_OBJECTCLASS_582=Configuration entry %s does \
|
### not contain the ds-cfg-group-implementation objectclass, which is required \
|
### for group implementation definitions
|
INFO_CONFIG_GROUP_DESCRIPTION_CLASS_NAME_583=\u7528\u4e8e\u5b9a\u4e49\u76ee\u5f55\u670d\u52a1\u5668\u7ec4\u5b9e\u73b0\u7684 Java \u7c7b\u7684\u5168\u9650\u5b9a\u540d\u79f0\u3002\u5982\u679c\u5728\u542f\u7528\u5173\u8054\u7684\u5b9e\u73b0\u65f6\u66f4\u6539\u4e86\u8be5\u540d\u79f0\uff0c\u5219\u5fc5\u987b\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u7ec4\u5b9e\u73b0\u4ee5\u4f7f\u66f4\u6539\u751f\u6548
|
###SEVERE_ERR_CONFIG_GROUP_NO_CLASS_NAME_584=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated group implementation
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_NAME_585=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_586=Class %s specified in configuration \
|
### entry %s does not contain a valid group implementation: %s
|
INFO_CONFIG_GROUP_DESCRIPTION_ENABLED_587=\u6307\u793a\u662f\u5426\u5e94\u542f\u7528\u8be5\u76ee\u5f55\u670d\u52a1\u5668\u7ec4\u5b9e\u73b0\u3002\u5bf9\u6b64\u5c5e\u6027\u7684\u66f4\u6539\u5c06\u7acb\u5373\u751f\u6548
|
###SEVERE_ERR_CONFIG_GROUP_NO_ENABLED_ATTR_588=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the group \
|
### implementation should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_ENABLED_VALUE_589=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_GROUP_CLASS_ACTION_REQUIRED_590=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u7ec4\u5b9e\u73b0\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u7ec4\u5b9e\u73b0\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_GROUP_INITIALIZATION_FAILED_591=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u7684\u7ec4\u5b9e\u73b0\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_GROUP_EXISTS_592=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u7ec4\u5b9e\u73b0\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u7ec4\u5b9e\u73b0
|
###SEVERE_ERR_CONFIG_GROUP_UNACCEPTABLE_CONFIG_593=The configuration for the \
|
### group implementation defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_ROOTDN_DESCRIPTION_ROOT_PRIVILEGE_594=Set of \
|
### privileges that should automatically be assigned to root users when they \
|
### authenticate to the server
|
###SEVERE_WARN_CONFIG_ROOTDN_UNRECOGNIZED_PRIVILEGE_595=The set of default root \
|
### privileges contained in configuration attribute %s of entry %s contains an \
|
### unrecognized privilege %s
|
###SEVERE_ERR_CONFIG_ROOTDN_ERROR_DETERMINING_ROOT_PRIVILEGES_596=An error \
|
### occurred while attempting to determine the set of privileges that root users \
|
### should be granted by default: %s
|
INFO_CONFIG_ROOTDN_UPDATED_PRIVILEGES_597=\u5df2\u66f4\u65b0\u5c06\u81ea\u52a8\u5206\u914d\u7ed9\u8d85\u7ea7\u7528\u6237\u7684\u6743\u9650\u96c6\u3002\u8be5\u65b0\u6743\u9650\u96c6\u4e0d\u9002\u7528\u4e8e\u5df2\u4f5c\u4e3a\u8d85\u7ea7\u7528\u6237\u901a\u8fc7\u9a8c\u8bc1\u7684\u4efb\u4f55\u73b0\u6709\u8fde\u63a5\uff0c\u4f46\u5c06\u7528\u4e8e\u6240\u6709\u540e\u7eed\u8d85\u7ea7\u7528\u6237\u9a8c\u8bc1
|
MILD_ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES_598=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u6dfb\u52a0\u64cd\u4f5c
|
MILD_ERR_CONFIG_FILE_DELETE_INSUFFICIENT_PRIVILEGES_599=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u5220\u9664\u64cd\u4f5c
|
MILD_ERR_CONFIG_FILE_MODIFY_INSUFFICIENT_PRIVILEGES_600=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u4fee\u6539\u64cd\u4f5c
|
MILD_ERR_CONFIG_FILE_MODDN_INSUFFICIENT_PRIVILEGES_601=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u4fee\u6539 DN \u64cd\u4f5c
|
MILD_ERR_CONFIG_FILE_SEARCH_INSUFFICIENT_PRIVILEGES_602=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u5728\u76ee\u5f55\u670d\u52a1\u5668\u914d\u7f6e\u4e2d\u6267\u884c\u641c\u7d22\u64cd\u4f5c
|
MILD_ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES_603=\u60a8\u6ca1\u6709\u8db3\u591f\u7684\u6743\u9650\u66f4\u6539\u9ed8\u8ba4\u8d85\u7ea7\u7528\u6237\u6743\u9650\u96c6
|
###FATAL_ERR_CONFIG_CERTMAPPER_CANNOT_GET_BASE_604=An error occurred while \
|
### attempting to retrieve the certificate mapper base entry cn=Certificate \
|
### Mappers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_CERTMAPPER_BASE_DOES_NOT_EXIST_605=The certificate mapper \
|
### configuration base cn=Certificate Mappers,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_CERTMAPPER_ENTRY_UNACCEPTABLE_606=Configuration entry %s \
|
### does not contain a valid certificate mapper configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_CERTMAPPER_CANNOT_CREATE_MAPPER_607=An error occurred while \
|
### attempting to create a Directory Server certificate mapper from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_OBJECTCLASS_608=Configuration entry %s \
|
### does not contain the ds-cfg-certificate-mapper objectclass, which is required \
|
### for certificate mapper definitions
|
###SEVERE_ERR_CONFIG_CERTMAPPER_NO_CLASS_NAME_609=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated certificate mapper
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_NAME_610=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_611=Class %s specified in \
|
### configuration entry %s does not contain a valid certificate mapper \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_ENABLED_VALUE_612=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_CERTMAPPER_CLASS_ACTION_REQUIRED_613=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u8bc1\u4e66\u6620\u5c04\u5668\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u6620\u5c04\u5668\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED_614=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8bc1\u4e66\u6620\u5c04\u5668\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_CERTMAPPER_EXISTS_615=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u8bc1\u4e66\u6620\u5c04\u5668\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u6620\u5c04\u5668
|
###SEVERE_ERR_CONFIG_CERTMAPPER_UNACCEPTABLE_CONFIG_616=The configuration for \
|
### the certificate mapper defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_KEYMANAGER_CANNOT_GET_BASE_617=An error occurred while \
|
### attempting to retrieve the key manager provider base entry cn=Key Manager \
|
### Providers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_KEYMANAGER_BASE_DOES_NOT_EXIST_618=The key manager \
|
### provider configuration base cn=Key Manager Providers,cn=config does not exist \
|
### in the Directory Server configuration. This entry must be present for the \
|
### server to function properly
|
###SEVERE_ERR_CONFIG_KEYMANAGER_ENTRY_UNACCEPTABLE_619=Configuration entry %s \
|
### does not contain a valid key manager provider configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_KEYMANAGER_CANNOT_CREATE_PROVIDER_620=An error occurred \
|
### while attempting to create a Directory Server key manager provider from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_OBJECTCLASS_621=Configuration entry %s \
|
### does not contain the ds-cfg-key-manager-provider objectclass, which is \
|
### required for key manager provider definitions
|
###SEVERE_ERR_CONFIG_KEYMANAGER_NO_CLASS_NAME_622=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated key manager provider
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_NAME_623=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_624=Class %s specified in \
|
### configuration entry %s does not contain a valid key manager provider \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_ENABLED_VALUE_625=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_KEYMANAGER_CLASS_ACTION_REQUIRED_626=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u63d0\u4f9b\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED_627=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_KEYMANAGER_EXISTS_628=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u63d0\u4f9b\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_KEYMANAGER_UNACCEPTABLE_CONFIG_629=The configuration for \
|
### the key manager provider defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_TRUSTMANAGER_CANNOT_GET_BASE_630=An error occurred while \
|
### attempting to retrieve the trust manager provider base entry cn=Trust Manager \
|
### Providers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_TRUSTMANAGER_BASE_DOES_NOT_EXIST_631=The trust manager \
|
### provider configuration base cn=Trust Manager Providers,cn=config does not \
|
### exist in the Directory Server configuration. This entry must be present for \
|
### the server to function properly
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_ENTRY_UNACCEPTABLE_632=Configuration entry %s \
|
### does not contain a valid trust manager provider configuration: %s. It will \
|
### be ignored
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_CANNOT_CREATE_PROVIDER_633=An error occurred \
|
### while attempting to create a Directory Server trust manager provider from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_OBJECTCLASS_634=Configuration entry %s \
|
### does not contain the ds-cfg-trust-manager-provider objectclass, which is \
|
### required for trust manager provider definitions
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_CLASS_NAME_635=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated trust manager provider
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_NAME_636=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_637=Class %s specified in \
|
### configuration entry %s does not contain a valid trust manager provider \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_ENABLED_VALUE_638=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: \
|
### %s
|
INFO_CONFIG_TRUSTMANAGER_CLASS_ACTION_REQUIRED_639=\u65e0\u6cd5\u5728\u914d\u7f6e\u6761\u76ee %3$s \u4e2d\u52a8\u6001\u5e94\u7528\u8bf7\u6c42\u7684\u4fe1\u4efb\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7c7b\u540d\u66f4\u6539\uff08\u4ece %1$s \u66f4\u6539\u4e3a %2$s\uff09\u3002\u5728\u7981\u7528\u5e76\u91cd\u65b0\u542f\u7528\u8be5\u63d0\u4f9b\u7a0b\u5e8f\u6216\u91cd\u65b0\u542f\u52a8\u76ee\u5f55\u670d\u52a1\u5668\u540e\uff0c\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
MILD_ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED_640=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u4fe1\u4efb\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
MILD_ERR_CONFIG_TRUSTMANAGER_EXISTS_641=\u65e0\u6cd5\u6dfb\u52a0 DN \u4e3a %s \u7684\u65b0\u4fe1\u4efb\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u6761\u76ee\uff0c\u56e0\u4e3a\u5df2\u6ce8\u518c\u5177\u6709\u8be5 DN \u7684\u63d0\u4f9b\u7a0b\u5e8f
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_UNACCEPTABLE_CONFIG_642=The configuration for \
|
### the trust manager provider defined in configuration entry %s was not \
|
### acceptable according to its internal validation. However, no specific \
|
### information is available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTE_643=Unable to retrieve JMX \
|
### attribute %s associated with configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_JMX_SET_ATTR_NO_CONNECTION_644=Unable to set the value of \
|
### JMX attribute %s associated with configuration entry %s because no JMX \
|
### connection is available
|
###SEVERE_ERR_CONFIG_CHANGE_NO_RESULT_645=%s.%s returned a result of null for \
|
### entry %s
|
###SEVERE_ERR_CONFIG_CHANGE_RESULT_ERROR_646=%s.%s failed for entry %s: result \
|
### code=%s, admin action required=%b, messages="%s"
|
###SEVERE_WARN_CONFIG_CHANGE_RESULT_ACTION_REQUIRED_647=%s.%s indicated that \
|
### administrative action is required for entry %s: messages="%s"
|
INFO_CONFIG_CHANGE_RESULT_MESSAGES_648=\u5bf9\u6761\u76ee %3$s \u6267\u884c\u7684 %1$s.%2$s \u6210\u529f\uff0c\u4f46\u751f\u6210\u4e86\u4ee5\u4e0b\u6d88\u606f: %4$s
|
###SEVERE_ERR_CONFIG_VATTR_INVALID_SEARCH_FILTER_649=Unable to parse value "%s" \
|
### from config entry "%s" as a valid search filter: %s
|
###SEVERE_ERR_CONFIG_VATTR_INITIALIZATION_FAILED_650=An error occurred while \
|
### trying to load an instance of class %s referenced in configuration entry %s \
|
### as a virtual attribute provider: %s
|
###SEVERE_ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDER_651=The virtual attribute \
|
### configuration in entry "%s" is not valid because attribute type %s is \
|
### single-valued but provider %s may generate multiple values
|
###SEVERE_ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUES_652=The virtual attribute \
|
### configuration in entry "%s" is not valid because attribute type %s is \
|
### single-valued but the conflict behavior is configured to merge real and \
|
### virtual values
|
MILD_ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWED_653=\u65e0\u6cd5\u4fee\u6539\u914d\u7f6e\u6761\u76ee %s\uff0c\u56e0\u4e3a\u8be5\u53d8\u66f4\u4f1a\u66f4\u6539\u5176\u7ed3\u6784\u5316\u5bf9\u8c61\u7c7b
|
###FATAL_ERR_CONFIG_CANNOT_CALCULATE_DIGEST_654=An error occurred while \
|
### attempting to calculate a SHA-1 digest of file %s: %s
|
###SEVERE_WARN_CONFIG_MANUAL_CHANGES_DETECTED_655=The Directory Server has \
|
### detected that one or more external changes have been made to the \
|
### configuration file %s while the server was online, but another change has \
|
### caused the server configuration to be overwritten. The manual changes have \
|
### not been applied, but they have been preserved in file %s
|
###SEVERE_ERR_CONFIG_MANUAL_CHANGES_LOST_656=The Directory Server encountered an \
|
### error while attempting to determine whether the configuration file %s has \
|
### been externally edited with the server online, and/or trying to preserve such \
|
### changes: %s. Any manual changes made to that file may have been lost
|
###SEVERE_ERR_CONFIG_ROTATION_POLICY_INVALID_CLASS_657=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server log rotation policy: %s
|
###SEVERE_ERR_CONFIG_RETENTION_POLICY_INVALID_CLASS_658=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server log retention policy: %s
|
###SEVERE_ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICY_659=An error occurred \
|
### while attempting to create a Directory Server log rotation policy from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICY_660=An error occurred \
|
### while attempting to create a Directory Server log retention policy from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITER_661=An error occurred while \
|
### attempting to create a text writer for a Directory Server logger from the \
|
### information in configuration entry %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_MULTIPLE_ENTRIES_IN_FILE_662=Schema configuration \
|
### file %s in directory %s contains more than one entry. Only the first entry \
|
### will be examined, and the additional entries will be ignored
|
###SEVERE_WARN_CONFIG_SCHEMA_UNPARSEABLE_EXTRA_DATA_IN_FILE_663=Schema \
|
### configuration file %s in directory %s contains additional data after the \
|
### schema entry that cannot be parsed by the LDIF reader: %s. The first entry \
|
### will be processed, but the remaining data will be ignored
|
###SEVERE_WARN_CONFIG_PLUGIN_EMPTY_ELEMENT_IN_ORDER_664=The plugin order \
|
### definition for plugins of type %s contains an empty element. This may cause \
|
### the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_MULTIPLE_WILDCARDS_IN_ORDER_665=The plugin order \
|
### definition for plugins of type %s contains multiple wildcard characters. All \
|
### plugin definitions should contain exactly one wildcard element to indicate \
|
### where unmatched plugins should be included in the order, and including \
|
### multiple wildcards may cause the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_LISTED_MULTIPLE_TIMES_666=The plugin order \
|
### definition for plugins of type %s includes multiple references to the '%s' \
|
### plugin. This may cause the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_ORDER_NO_WILDCARD_667=The plugin order definition \
|
### for plugins of type %s does not include a wildcard element to indicate where \
|
### unmatched plugins should be included in the order. The server will default \
|
### to invoking all unnamed plugins after set of named plugins
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_SYNTAX_IN_USE_668=Attribute syntax %s \
|
### cannot be deleted from the server because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_SYNTAX_IN_USE_669=Attribute syntax \
|
### %s cannot be disabled because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_MR_IN_USE_BY_AT_670=Matching rule %s \
|
### cannot be deleted from the server because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_MR_IN_USE_BY_MRU_671=Matching rule %s \
|
### cannot be deleted from the server because it is in use by matching rule use \
|
### %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_MR_IN_USE_BY_AT_672=Matching rule %s \
|
### cannot be disabled because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_MR_IN_USE_BY_MRU_673=Matching rule \
|
### %s cannot be disabled because it is in use by matching rule use %s
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILED_674=Unable to initialize \
|
### an instance of class %s as a work queue as specified in configuration entry \
|
### %s: %s
|
INFO_CONFIG_WORK_QUEUE_CLASS_CHANGE_REQUIRES_RESTART_675=\u7528\u4e8e\u63d0\u4f9b\u76ee\u5f55\u670d\u52a1\u5668\u5de5\u4f5c\u961f\u5217\u5b9e\u73b0\u7684\u7c7b\u5df2\u4ece %s \u66f4\u6539\u4e3a %s\uff0c\u4f46\u5728\u91cd\u65b0\u542f\u52a8\u670d\u52a1\u5668\u540e\u8be5\u66f4\u6539\u624d\u4f1a\u751f\u6548
|
###SEVERE_ERR_CONFIG_FILE_ADD_APPLY_FAILED_676=The attempt to apply the \
|
### configuration add failed. The preliminary checks were all successful and the \
|
### entry was added to the server configuration, but at least one of the \
|
### configuration add listeners reported an error when attempting to apply the \
|
### change: %s
|
###SEVERE_ERR_CONFIG_FILE_DELETE_APPLY_FAILED_677=The attempt to apply the \
|
### configuration delete failed. The preliminary checks were all successful and \
|
### the entry was removed from the server configuration, but at least one of the \
|
### configuration delete listeners reported an error when attempting to apply the \
|
### change: %s
|
###SEVERE_ERR_CONFIG_FILE_MODIFY_APPLY_FAILED_678=The attempt to apply the \
|
### configuration modification failed. The preliminary checks were all \
|
### successful and the modified entry was written to the server configuration, \
|
### but at least one of the configuration change listeners reported an error when \
|
### attempting to apply the change: %s
|
MILD_ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLE_679=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u94a5\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLE_680=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u4fe1\u4efb\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLE_681=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u4fe1\u4efb\u7ba1\u7406\u5668\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLE_682=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5e10\u6237\u72b6\u6001\u901a\u77e5\u5904\u7406\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_SCHEMA_SYNTAX_CONFIG_NOT_ACCEPTABLE_683=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5c5e\u6027\u8bed\u6cd5\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLE_684=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8bc1\u4e66\u6620\u5c04\u5668\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_GROUP_CONFIG_NOT_ACCEPTABLE_686=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u7ec4\u5b9e\u73b0\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLE_687=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8eab\u4efd\u6620\u5c04\u5668\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_SCHEMA_MR_CONFIG_NOT_ACCEPTABLE_688=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5339\u914d\u89c4\u5219\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLE_689=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u751f\u6210\u5668\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLE_690=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u5b58\u50a8\u65b9\u6848\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLE_691=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u5bc6\u7801\u9a8c\u8bc1\u5668\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLE_692=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u63d2\u4ef6\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLE_693=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684 SASL \u673a\u5236\u5904\u7406\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLE_694=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u865a\u62df\u5c5e\u6027\u63d0\u4f9b\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLE_695=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8b66\u62a5\u5904\u7406\u7a0b\u5e8f\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILED_696=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u8b66\u62a5\u5904\u7406\u7a0b\u5e8f\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SMTP_SERVER_697=The provided SMTP server value \
|
### '%s' is invalid. An SMTP server value must have an IP address or a \
|
### resolvable name, and it may optionally be followed by a colon and an integer \
|
### value between 1 and 65535 to specify the server port number
|
###SEVERE_ERR_STARTOK_CANNOT_OPEN_FOR_READING_698=An error occurred while \
|
### attempting to open the current configuration file %s for reading in order to \
|
### copy it to the ".startok" file: %s
|
###SEVERE_ERR_STARTOK_CANNOT_OPEN_FOR_WRITING_699=An error occurred while \
|
### attempting to open file %s in order to write the ".startok" configuration \
|
### file: %s
|
###SEVERE_ERR_STARTOK_CANNOT_WRITE_700=An error occurred while attempting to \
|
### copy the current configuration from file %s into temporary file %s for use \
|
### as the ".startok" configuration file: %s
|
###SEVERE_ERR_STARTOK_CANNOT_RENAME_701=An error occurred while attempting to \
|
### rename file %s to %s for use as the ".startok" configuration file: %s
|
NOTICE_CONFIG_FILE_USING_STARTOK_FILE_702=\u76ee\u5f55\u670d\u52a1\u5668\u6b63\u5728\u4f7f\u7528\u6700\u8fd1\u7684\u5df2\u77e5\u6b63\u786e\u914d\u7f6e\u6587\u4ef6 %s \u8fdb\u884c\u542f\u52a8\uff0c\u800c\u4e0d\u662f\u4f7f\u7528\u6d3b\u52a8\u914d\u7f6e\u6587\u4ef6 %s
|
###SEVERE_WARN_CONFIG_FILE_NO_STARTOK_FILE_703=No last known good configuration \
|
### file %s exists. The server will attempt to start using the active \
|
### configuration file %s
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_INVALID_704=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: %s
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_INVALID_FORM_705=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### does not follow a singular property=value form
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIG_706=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### shadows configuration attribute %s
|
###SEVERE_ERR_CONFIG_JE_DUPLICATE_PROPERTY_707=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### is already defined for this component
|
INFO_CONFIG_JE_PROPERTY_REQUIRES_RESTART_708=\u5728\u91cd\u65b0\u542f\u52a8\u8bbe\u7f6e\u4e86 Berkeley \u6570\u636e\u5e93 JE \u5c5e\u6027 %s \u7684\u7ec4\u4ef6\u540e\uff0c\u8be5\u5c5e\u6027\u7684\u8bbe\u7f6e\u624d\u4f1a\u751f\u6548
|
###SEVERE_ERR_CONFIG_LOGGING_CANNOT_OPEN_FILE_709=An error occurred while \
|
### attempting to open the configured log file %s for logger %s: %s
|
###SEVERE_ERR_CONFIG_WORKFLOW_ELEMENT_CONFIG_NOT_ACCEPTABLE_710=The configuration \
|
### for the workflow element defined in configuration entry %s was not \
|
### acceptable: %s
|
###SEVERE_ERR_CONFIG_WORKFLOW_ELEMENT_CANNOT_INITIALIZE_711=An error occurred \
|
### while trying to initialize a workflow element from class %s with the \
|
### information in configuration entry %s: %s. This workflow element will be \
|
### disabled
|
MILD_ERR_CONFIG_WORKFLOW_ELEMENT_ALREADY_REGISTERED_712=\u5df2\u5728\u76ee\u5f55\u670d\u52a1\u5668\u4e2d\u6ce8\u518c\u4e86\u5de5\u4f5c\u6d41\u5143\u7d20 %s\u3002\u5c06\u5ffd\u7565\u8be5\u5de5\u4f5c\u6d41\u5143\u7d20
|
###SEVERE_ERR_CONFIG_WORKFLOW_CANNOT_CONFIGURE_MANUAL_713=An error occurred \
|
### while trying to configure in manual mode the workflows in the \
|
### Directory Server, and rollback to automatic configuration mode has failed \
|
### too. If the server is in an unstab\
|
### le state restart it with the last \
|
### valid configuration
|
###SEVERE_ERR_CONFIG_WORKFLOW_CANNOT_CONFIGURE_AUTO_714=An error occurred \
|
### while trying to configure in automatic mode the workflows in the \
|
### Directory Server, and rollback to manual configuration mode has failed \
|
### too. If the server is in an unstable state restart it with the last \
|
### valid configuration
|
###SEVERE_ERR_CONFIG_LOGGING_INSANE_MODE_715=Invalid UNIX file permissions %s \
|
### does not allow write access to the log file by the log publisher
|
###SEVERE_ERR_CONFIG_LOGGING_MODE_INVALID_716=Invalid UNIX file permissions %s: %s
|
MILD_ERR_CONFIG_EXTENSION_CONFIG_NOT_ACCEPTABLE_717=\u65e0\u6cd5\u63a5\u53d7\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u6269\u5c55\u7684\u914d\u7f6e: %s
|
MILD_ERR_CONFIG_EXTENSION_INITIALIZATION_FAILED_718=\u5728\u5c1d\u8bd5\u5c06\u7c7b %s \u7684\u5b9e\u4f8b\u521d\u59cb\u5316\u4e3a\u914d\u7f6e\u6761\u76ee %s \u4e2d\u5b9a\u4e49\u7684\u6269\u5c55\u65f6\u51fa\u73b0\u9519\u8bef: %s
|
###SEVERE_ERR_CONFIG_NETWORKGROUPREQUESTFILTERINGPOLICY_INVALID_ATTRIBUTE_719=The \
|
### allowed attribute %s specified in configuration entry %s is also defined as \
|
### a prohibited attribute
|
###SEVERE_ERR_CONFIG_NETWORKGROUPREQUESTFILTERINGPOLICY_INVALID_SUBTREE_720=The \
|
### allowed subtree %s specified in configuration entry %s is also defined as \
|
### a prohibited subtree
|
###SEVERE_ERR_CONFIG_NETWORK_GROUP_CONFIG_NOT_ACCEPTABLE_721=The configuration \
|
### for the network group defined in configuration entry %s was not acceptable: %s
|
###SEVERE_ERR_CONFIG_NETWORK_GROUP_POLICY_CANNOT_INITIALIZE_722=An error occurred \
|
### while trying to initialize a network group policy loaded from class %s with \
|
### the information in configuration entry %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_LDAP_SYNTAX_723=An ldapSyntaxes \
|
### attribute read from schema configuration file %s could not be parsed: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_LDAP_SYNTAX_724=An ldap syntax read \
|
### from schema configuration file %s conflicts with another ldap syntax already \
|
### read into the schema: %s. The later ldap syntax description will be used
|
