From 67405dde9ba213331dab1fc46cb18c485070fd5b Mon Sep 17 00:00:00 2001 From: matthew_swift <matthew_swift@localhost> Date: Fri, 05 Jun 2009 09:04:50 +0000 Subject: [PATCH] svn merge -r5333:5417 https://opends.dev.java.net/svn/opends/branches/b2.0 --- opends/src/messages/messages/config_fr.properties | 1851 +++++++++++++++++++++++++++++++++++++++++++++-------------- 1 files changed, 1,395 insertions(+), 456 deletions(-) diff --git a/opends/src/messages/messages/config_fr.properties b/opends/src/messages/messages/config_fr.properties index 9f7f906..a0dfd33 100644 --- a/opends/src/messages/messages/config_fr.properties +++ b/opends/src/messages/messages/config_fr.properties @@ -21,14 +21,10 @@ # CDDL HEADER END # # Copyright 2006-2009 Sun Microsystems, Inc. - - - # # Global directives # global.category=CONFIG - # # Format string definitions # @@ -57,7 +53,7 @@ MILD_ERR_CONFIG_ATTR_NO_INT_VALUE_8=Impossible de r\u00e9cup\u00e9rer la valeur de l'attribut de configuration %s en tant que nombre entier car cet attribut n'a aucune valeur MILD_ERR_CONFIG_ATTR_MULTIPLE_INT_VALUES_9=Impossible de r\u00e9cup\u00e9rer la valeur de l'attribut de configuration %s en tant que nombre entier car cet attribut a plusieurs valeurs MILD_ERR_CONFIG_ATTR_VALUE_OUT_OF_INT_RANGE_10=Impossible de r\u00e9cup\u00e9rer la valeur de l'attribut de configuration %s en tant que int Java car la valeur est en dehors de la plage autoris\u00e9e pour un int -MILD_ERR_CONFIG_ATTR_INVALID_INT_VALUE_11=Impossible de d\u00e9finir la valeur de l'attribut %s de configuration de nombre entier car la valeur fournie %s ne peut pas \u00eatre interpr\u00e9t\u00e9e comme un entier : %s +MILD_ERR_CONFIG_ATTR_INVALID_INT_VALUE_11=Impossible de d\u00e9finir la valeur de l'attribut %s de configuration de nombre entier car la valeur fournie %s ne peut pas \u00eatre interpr\u00e9t\u00e9e comme un entier\u00a0: %s MILD_ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUND_12=Impossible de d\u00e9finir la valeur de l'attribut de configuration %s car la valeur fournie %d est inf\u00e9rieure \u00e0 la valeur minimale autoris\u00e9e %d MILD_ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUND_13=Impossible de d\u00e9finir la valeur de l'attribut de configuration %s car la valeur fournie %d est sup\u00e9rieure \u00e0 la valeur maximale autoris\u00e9e %d MILD_ERR_CONFIG_ATTR_INT_COULD_NOT_PARSE_14=Impossible d'analyser la valeur %s de l'attribut de configuration %s en tant que valeur d'entier\u00a0: %s @@ -72,44 +68,99 @@ MILD_ERR_CONFIG_ENTRY_CONFLICTING_CHILD_23=Impossible d'ajouter une entr\u00e9e de configuration %s en tant qu'enfant d'une entr\u00e9e de configuration %s car une entr\u00e9e d'enfant a d\u00e9j\u00e0 \u00e9t\u00e9 trouv\u00e9e avec ce DN MILD_ERR_CONFIG_ENTRY_NO_SUCH_CHILD_24=Impossible de supprimer une entr\u00e9e %s en tant qu'enfant d'une entr\u00e9e de configuration %s car cette entr\u00e9e n'a pas d'enfant avec le DN sp\u00e9cifi\u00e9 MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_NONLEAF_25=Impossible de supprimer une entr\u00e9e %s en tant qu'enfant d'une entr\u00e9e de configuration %s car cette entr\u00e9e a elle-m\u00eame des enfants et que des entr\u00e9es non-terminales ne doivent pas \u00eatre supprim\u00e9es -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 +###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=Attribut de configuration invalide %s d\u00e9tect\u00e9\u00a0: la seule option d'attribut autoris\u00e9e dans la configuration de Directory Server est "pending" pour indiquer le jeu de valeurs en attente -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=There are no active debug loggers defined in the Directory Server configuration. No debug logging will be performed -SEVERE_ERR_CONFIG_LOGGER_ENTRY_UNACCEPTABLE_47=Configuration entry %s does not contain a valid logger configuration: %s. It will be ignored +###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=Il n'y a pas de journal de deboguage actif d\u00e9fini dans la configuration de Directory Server. Aucune connexion de d\u00e9boguage ne sera eeffectu\u00e9e. +###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=Raison inconnue inacceptable -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 +###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=Le nom complet de la classe Java d\u00e9finissant le journal de Directory Server. En cas de changement alors que le journal associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce journal de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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=Indique si une certaine flexibilit\u00e9 doit \u00eatre autoris\u00e9e dans les caract\u00e8res pouvant \u00eatre utilis\u00e9s pour les noms d'attributs. Par d\u00e9faut, les noms d'attributs peuvent uniquement contenir des lettres alphab\u00e9tiques ASCII, des chiffres num\u00e9riques et tirets et doivent commencer par une lettre. Si les exceptions de nom d'attribut sont activ\u00e9es, le caract\u00e8re de soulignement sera \u00e9galement autoris\u00e9 et le nom d'attribut pourra aussi commencer par un chiffre. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Comportement \u00e0 adopter par Directory Server s'il d\u00e9couvre un attribut dont la valeur n'est pas conforme \u00e0 la syntaxe pour cet attribut. Les valeurs acceptables pour cet attribut sont "reject" pour refuser la valeur invalide, "warn" pour accepter la valeur invalide tout en journalisant un message d'avertissement ou "accept" pour accepter la valeur invalide sans aucune avertissement. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Indique si une certaine flexibilit\u00e9 doit \u00eatre autoris\u00e9e dans les caract\u00e8res pouvant \u00eatre utilis\u00e9s pour les noms d'attributs. Par d\u00e9faut, les noms d'attributs peuvent uniquement contenir des lettres alphab\u00e9tiques ASCII, des chiffres num\u00e9riques et tirets et doivent commencer par une lettre. Si les exceptions de nom d'attribut sont activ\u00e9es, le caract\u00e8re de soulignement sera \u00e9galement autoris\u00e9 et le nom d'attribut pourra aussi commencer par un chiffre. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Comportement \u00e0 adopter par Directory Server s'il d\u00e9couvre un attribut dont la valeur n'est pas conforme \u00e0 la syntaxe pour cet attribut. Les valeurs acceptables pour cet attribut sont "reject" pour refuser la valeur invalide, "warn" pour accepter la valeur invalide tout en journalisant un message d'avertissement ou "accept" pour accepter la valeur invalide sans aucune avertissement. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=L'attribut de configuration %s semble contenir plusieurs jeux de valeurs en attente MILD_ERR_CONFIG_ATTR_MULTIPLE_ACTIVE_VALUE_SETS_65=L'attribut de configuration %s semble contenir plusieurs jeux de valeurs actives MILD_ERR_CONFIG_ATTR_NO_ACTIVE_VALUE_SET_66=L'attribut de configuration %s ne contient pas de jeu de valeurs actives @@ -128,181 +179,474 @@ MILD_ERR_CONFIG_CANNOT_GET_CONFIG_ENTRY_79=Une erreur s'est produite lors de la tentative de r\u00e9cup\u00e9ration d'une entr\u00e9e de configuration %s\u00a0: %s INFO_CONFIG_SET_ATTRIBUTE_80=La valeur de l'attribut de configuration %s a \u00e9t\u00e9 d\u00e9finie sur %s dans l'entr\u00e9e de configuration %s MILD_ERR_CONFIG_CHANGE_NOT_SUCCESSFUL_81=La tentative de mise \u00e0 jour de l'entr\u00e9e de configuration %s n'a pas r\u00e9ussi et un ou plusieurs probl\u00e8mes se sont pr\u00e9sent\u00e9s\u00a0: %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 +###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=Nombre de threads de travail \u00e0 utiliser pour les requ\u00eates de traitement, qui contr\u00f4lent le nombre d'op\u00e9rations que le serveur peut traiter simultan\u00e9ment. La valeur optimale d\u00e9pend du type de syst\u00e8me sur lequel le serveur tourne et de la charge de travail qu'il doit traiter, tout en \u00e9tant plut\u00f4t d\u00e9termin\u00e9 par des tests de rendement. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte INFO_CONFIG_WORK_QUEUE_DESCRIPTION_MAX_CAPACITY_86=Le nombre maximum de requ\u00eates en attente pouvant \u00eatre trait\u00e9es dans la file d'attente \u00e0 tout moment pendant que tous les threads de travail sont occup\u00e9s \u00e0 traiter d'autres op\u00e9rations. Si la limite est atteinte, toute nouvelle requ\u00eate sera refus\u00e9e. 0 indique qu'il n'y a aucune limite. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=%d threads de travail suppl\u00e9mentaires ont \u00e9t\u00e9 cr\u00e9\u00e9s pour porter le nombre total de threads disponibles \u00e0 %d INFO_CONFIG_WORK_QUEUE_DESTROYING_THREADS_92=%d threads de travail vont s'arr\u00eater d\u00e8s que possible afin de porter le nombre total de threads disponibles \u00e0 %d (l'arr\u00eat r\u00e9el peut prendre quelques secondes) INFO_CONFIG_WORK_QUEUE_NEW_CAPACITY_93=La capacit\u00e9 de la file d'attente a \u00e9t\u00e9 mise \u00e0 jour pour prendre en compte la nouvelle valeur %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 +###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=Le nom du r\u00e9pertoire o\u00f9 sont stock\u00e9s les fichiers de bases de donn\u00e9es de backend -SEVERE_ERR_CONFIG_BACKEND_NO_DIRECTORY_97=Configuration entry %s does not contain a valid value for configuration attribute ds-cfg-db-directory +###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=Une valeur null a \u00e9t\u00e9 fournie pour un attribut de configuration de DN %s MILD_ERR_CONFIG_ATTR_DN_CANNOT_PARSE_99=Une erreur s'est produite lors d'une tentative d'analyse de la valeur "%s" d'un attribut %s en tant que DN\u00a0: %s MILD_ERR_CONFIG_ATTR_INVALID_DN_VALUE_100=Impossible d'analyser la valeur %s de l'attribut de configuration %s en tant que DN\u00a0: %s MILD_ERR_CONFIG_ATTR_DN_INVALID_TYPE_101=Impossible d'analyser la valeur %s de l'attribut de configuration %s en tant que DN car l'\u00e9l\u00e9ment \u00e9tait d'un type invalide (%s) MILD_ERR_CONFIG_ATTR_DN_INVALID_ARRAY_TYPE_102=Impossible d'analyser la valeur de l'attribut de configuration %s en tant que jeu de valeurs de DN car le tableau contenait des \u00e9l\u00e9ments d'un type invalide (%s) -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 +###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=Indique si ce backend doit \u00eatre activ\u00e9 afin d'\u00eatre utilis\u00e9 dans Directory Server. Il est possible de modifier cela quand Directory Server est en ligne mais si un backend est d\u00e9sactiv\u00e9, il ne sera plus disponible INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_CLASS_109=Nom complet de la classe Java qui doit fournir la logique du serveur de base pour cette impl\u00e9mentation de backend. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que le backend n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que le serveur n'est pas red\u00e9marr\u00e9 -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 +###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=Ce backend d\u00e9fini dans l'entr\u00e9e de configuration %s est marqu\u00e9 comme d\u00e9sactiv\u00e9 et, par cons\u00e9quent, ne sera pas utilis\u00e9 -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 +###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=Le changement requis pour l'entr\u00e9e de configuration %s entra\u00eenerait la modification de la classe pour le backend associ\u00e9 de %s \u00e0 %s. Cette modification ne prend pas effet tant que le backend n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 NOTICE_CONFIG_BACKEND_CANNOT_REMOVE_BACKEND_WITH_SUBORDINATES_119=Le backend d\u00e9fini dans l'entr\u00e9e de configuration %s a un ou plusieurs backends subordonn\u00e9s. Il est impossible de supprimer un backend s'il a des backends subordonn\u00e9s -INFO_CONFIG_CORE_DESCRIPTION_MAX_ALLOWED_CONNECTIONS_120=Le nombre maximum de connexions clientes pouvant \u00eatre \u00e9tablies sur Directory Server \u00e0 un moment donn\u00e9. une valeur inf\u00e9rieure ou \u00e9gale \u00e0 z\u00e9ro indique qu'il ne devrait y avoir aucune limite. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte +INFO_CONFIG_CORE_DESCRIPTION_MAX_ALLOWED_CONNECTIONS_120=Le nombre maximum de connexions clientes pouvant \u00eatre \u00e9tablies sur Directory Server \u00e0 un moment donn\u00e9. une valeur inf\u00e9rieure ou \u00e9gale \u00e0 z\u00e9ro indique qu'il ne devrait y avoir aucune limite. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement INFO_CONFIG_LOGGER_CLASS_ACTION_REQUIRED_122=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du journal de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_LOGGER_EXISTS_123=Impossible d'ajouter une nouvelle entr\u00e9e de journal avec le DN %s car il y a d\u00e9j\u00e0 un journal enregistr\u00e9 avec ce DN MILD_ERR_CONFIG_LOGGER_ACCESS_INITIALIZATION_FAILED_124=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que journal d'acc\u00e8s, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_LOGGER_ERROR_INITIALIZATION_FAILED_125=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que journal d'erreur, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s -MILD_ERR_CONFIG_LOGGER_DEBUG_INITIALIZATION_FAILED_126=An error occurred while trying to initialize an instance of class %s as a debug logger as defined in configuration entry %s: %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 +MILD_ERR_CONFIG_LOGGER_DEBUG_INITIALIZATION_FAILED_126=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que journal de d\u00e9boguage, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %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=Le nom complet de la classe Java d\u00e9finissant le fournisseur de moniteur de Directory Server. En cas de changement alors que le moniteur associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce moniteur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce fournisseur de moniteur de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du moniteur de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le fournisseur de moniteur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_MONITOR_INITIALIZATION_FAILED_140=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que fournisseur de moniteur, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_MONITOR_EXISTS_141=Impossible d'ajouter une nouvelle entr\u00e9e de fournisseur de moniteur avec le DN %s car il y a d\u00e9j\u00e0 un fournisseur de moniteur enregistr\u00e9 avec ce DN -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 +###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=Indique si ce gestionnaire de connexion doit \u00eatre activ\u00e9 afin d'\u00eatre utilis\u00e9 dans Directory Server. Il est possible de modifier cela quand Directory Server est en ligne mais, si un gestionnaire de connexion est d\u00e9sactiv\u00e9, il ne sera plus disponible INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_CLASS_147=Nom complet de la classe Java devant fournir la logique du serveur de base pour cette impl\u00e9mentation de gestionnaire de connexion. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que le gestionnaire de connexion n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que le serveur n'est pas red\u00e9marr\u00e9 -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 +###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=Le gestionnaire de connexion d\u00e9fini dans l'entr\u00e9e de configuration %s est marqu\u00e9 comme d\u00e9sactiv\u00e9 et ne sera donc pas utilis\u00e9 -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 +###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=Indique si cette r\u00e8gle de correspondance doit \u00eatre activ\u00e9e afin d'\u00eatre utilis\u00e9e dans Directory Server. Il est possible de modifier cela quand Directory Server est en ligne mais, si une r\u00e8gle de correspondance est d\u00e9sactiv\u00e9e apr\u00e8s avoir \u00e9t\u00e9 utilis\u00e9e pour un ou plusieurs attributs, la correspondance risque de ne plus fonctionner comme elle le devrait avec ces attributs INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_CLASS_165=Nom complet de la classe Java devant fournir la logique du serveur de base pour cette impl\u00e9mentation de r\u00e8gle de correspondance. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que la r\u00e8gle de correspondance n'est pas d\u00e9sactiv\u00e9e puis r\u00e9activ\u00e9e ou que le serveur n'est pas red\u00e9marr\u00e9. De m\u00eame, des modifications dans la classe de r\u00e8gle de correspondance pour des r\u00e8gles de correspondance d\u00e9j\u00e0 utilis\u00e9es pour un ou plusieurs attributs peuvent entra\u00eener des r\u00e9sultats inattendus lors de la r\u00e9alisation de la correspondance pour ces attributs -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 +###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=La r\u00e8gle de correspondance d\u00e9finie dans l'entr\u00e9e de configuration %s est marqu\u00e9e comme d\u00e9sactiv\u00e9e et, par cons\u00e9quent, ne sera pas utilis\u00e9e. Si elle a \u00e9t\u00e9 utilis\u00e9e pr\u00e9c\u00e9demment pour un ou plusieurs attributs, la correspondance peut ne plus fonctionner pour des valeurs de ces attributs -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 +###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=Indique si cette syntaxe d'attribut doit \u00eatre activ\u00e9e afin d'\u00eatre utilis\u00e9e dans Directory Server. Il est possible de modifier cela quand Directory Server est en ligne mais, si une syntaxe est d\u00e9sactiv\u00e9e apr\u00e8s avoir \u00e9t\u00e9 utilis\u00e9e pour un ou plusieurs attributs, la correspondance risque de ne plus fonctionner comme elle le devrait avec ces attributs INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_CLASS_179=Nom complet de la classe Java devant fournir la logique du serveur de base pour cette impl\u00e9mentation de syntaxe d'attribut. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que la syntaxe n'est pas d\u00e9sactiv\u00e9e puis r\u00e9activ\u00e9e ou que le serveur n'est pas red\u00e9marr\u00e9. De m\u00eame, des modifications dans la classe de syntaxe pour des syntaxes d'attributs qui ont d\u00e9j\u00e0 \u00e9t\u00e9 utilis\u00e9es pour un ou plusieurs attributs peuvent entra\u00eener des r\u00e9sultats inattendus lors de la r\u00e9alisation de la correspondance pour ces attributs -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 +###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=La syntaxe d'attribut d\u00e9finie dans l'entr\u00e9e de configuration %s est marqu\u00e9e comme d\u00e9sactiv\u00e9e et, par cons\u00e9quent, ne sera pas utilis\u00e9e. Si elle a \u00e9t\u00e9 utilis\u00e9e pr\u00e9c\u00e9demment pour un ou plusieurs attributs, la correspondance peut ne plus fonctionner pour des valeurs de ces attributs -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 used to provide 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=Indique si Directory Server doit effectuer la v\u00e9rification du sch\u00e9ma pour des op\u00e9rations de mise \u00e0 jour afin de garantir la validit\u00e9 des entr\u00e9es, conform\u00e9ment \u00e0 la configuration du sch\u00e9ma du serveur (par ex., tous les attributs requis sont inclus et aucun attribut interdit n'est pr\u00e9sent). En g\u00e9n\u00e9ral, il n'est pas recommand\u00e9 de d\u00e9sactiver le sch\u00e9ma car des entr\u00e9es invalides peuvent alors \u00eatre autoris\u00e9es \u00e0 figurer dans le serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Indique si Directory Server doit effectuer la v\u00e9rification du sch\u00e9ma pour des op\u00e9rations de mise \u00e0 jour afin de garantir la validit\u00e9 des entr\u00e9es, conform\u00e9ment \u00e0 la configuration du sch\u00e9ma du serveur (par ex., tous les attributs requis sont inclus et aucun attribut interdit n'est pr\u00e9sent). En g\u00e9n\u00e9ral, il n'est pas recommand\u00e9 de d\u00e9sactiver le sch\u00e9ma car des entr\u00e9es invalides peuvent alors \u00eatre autoris\u00e9es \u00e0 figurer dans le serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=La configuration du fournisseur du moniteur de cache d'entr\u00e9es %s n'\u00e9tait pas disponible. De ce fait, ce fournisseur de moniteur %s ne sera pas activ\u00e9 INFO_WARN_CONFIG_ENTRYCACHE_MONITOR_CONFIG_DISABLED_206=La configuration du fournisseur de moniteur du cache d'entr\u00e9es %s \u00e9tait d\u00e9sactiv\u00e9e. De ce fait, le fournisseur de moniteur %s ne sera pas activ\u00e9 MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_CHILD_215=Une erreur inattendue s'est produite lors de la tentative de suppression d'une entr\u00e9e %s en tant qu'enfant de l'entr\u00e9e de configuration %s\u00a0: %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 +###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=L'attribut de configuration %s est en lecture seule et ses valeurs ne doivent pas \u00eatre modifi\u00e9es -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 +###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=Indique si ce plug-in doit \u00eatre activ\u00e9 afin d'\u00eatre utilis\u00e9 dans Directory Server. Il est possible de modifier cela quand Directory Server est en ligne, ce qui permet une prise d'effet imm\u00e9diate -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 +###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=Ce plug-in d\u00e9fini dans l'entr\u00e9e de configuration %s est marqu\u00e9 comme d\u00e9sactiv\u00e9 et, par cons\u00e9quent, ne sera pas utilis\u00e9 -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 +###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=Type(s) de plug-in pour ce plug-in, contr\u00f4lant les p\u00e9riodes auxquelles le plug-in sera appel\u00e9 pendant le traitement. Cette valeur est en lecture seule quand le plug-in est charg\u00e9 et initialis\u00e9. Les modifications de ces attributs ne prennent pas effet tant que le plug-in n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_CLASS_238=Nom complet de la classe Java devant fournir la logique du serveur de base pour cette impl\u00e9mentation de plug-in. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que le plug-in n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que le serveur n'est pas red\u00e9marr\u00e9 -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=Indique si Directory Server doit envoyer une r\u00e9ponse au client concernant les op\u00e9rations qui ont \u00e9t\u00e9 abandonn\u00e9es, afin de lui indiquer que le serveur a termin\u00e9 leur traitement. La sp\u00e9cification LDAP interdit d'envoyer une r\u00e9ponse dans ce genre de cas mais certains clients peuvent ne pas se comporter correctement s'ils attendent une r\u00e9ponse pour une op\u00e9ration, r\u00e9ponse qu'ils n'auront pas du fait de cet abandon. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Indique si Directory Server doit envoyer une r\u00e9ponse au client concernant les op\u00e9rations qui ont \u00e9t\u00e9 abandonn\u00e9es, afin de lui indiquer que le serveur a termin\u00e9 leur traitement. La sp\u00e9cification LDAP interdit d'envoyer une r\u00e9ponse dans ce genre de cas mais certains clients peuvent ne pas se comporter correctement s'ils attendent une r\u00e9ponse pour une op\u00e9ration, r\u00e9ponse qu'ils n'auront pas du fait de cet abandon. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que gestionnaire d'op\u00e9rations \u00e9tendues, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %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 +###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=Le nom complet de la classe Java d\u00e9finissant le gestionnaire du m\u00e9canisme SASL de Directory Server. En cas de changement alors que le gestionnaire associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce gestionnaire n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce gestionnaire du m\u00e9canisme SASL de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du gestionnaire du m\u00e9canisme SASL de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_SASL_INITIALIZATION_FAILED_277=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que gestionnaire de m\u00e9canisme SASL, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_SASL_EXISTS_278=Impossible d'ajouter une nouvelle entr\u00e9e de gestionnaire du m\u00e9canisme SASL avec le DN %s car il y a d\u00e9j\u00e0 un gestionnaire enregistr\u00e9 avec ce DN -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 +###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=Impossible d'ajouter l'entr\u00e9e %s \u00e0 la configuration de Directory Server car une autre entr\u00e9e de configuration existe d\u00e9j\u00e0 avec ce DN MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_DN_281=Impossible d'ajouter l'entr\u00e9e %s \u00e0 la configuration de Directory Server car le DN n'a pas de parent MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_282=Impossible d'ajouter l'entr\u00e9e %s \u00e0 la configuration de Directory Server car l'entr\u00e9e de son parent %s n'existe pas @@ -327,255 +671,675 @@ MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIG_301=Une erreur s'est produite lors de la tentative de changement de nom de la nouvelle configuration de Directory Server du fichier %s en %s\u00a0: %s MILD_ERR_CONFIG_FILE_MODDN_NOT_ALLOWED_302=Les op\u00e9rations de modification de DN ne sont pas autoris\u00e9es dans la configuration de Directory Server INFO_CONFIG_LOGGER_SUPPRESS_INTERNAL_OPERATIONS_303=Indique si des messages sur des op\u00e9rations internes doivent \u00eatre exclus du fichier journal d'acc\u00e8s -SEVERE_ERR_CONFIG_LOGGER_INVALID_SUPPRESS_INT_OPERATION_VALUE_304=Invalid value specified for attribute %s. Allowed values are true or false +###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=Jeu de DN de base \u00e0 utiliser pour ce backend. Selon l'impl\u00e9mentation du backend, les modifications de cet attribut pourront prendre effet automatiquement -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 +###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=Indique si le fournisseur de gestionnaire cl\u00e9 de Directory Server doit \u00eatre activ\u00e9. Un fournisseur de gestionnaire de cl\u00e9s est requis pour les op\u00e9rations n\u00e9cessitant un acc\u00e8s au gestionnaire de cl\u00e9s (par exemple, la communication par SSL). Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte mais elles influeront sur de futures tentatives d'acc\u00e8s au gestionnaire de cl\u00e9s -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. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Aucune strat\u00e9gie de retention de fichier n'a \u00e9t\u00e9 d\u00e9finie dans cette entr\u00e9e de configuration %s. Aucun fichier journal ne sera supprim\u00e9 -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 +###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=Aucune strat\u00e9gie de r\u00e9tention de fichier n'a \u00e9t\u00e9 d\u00e9finie dans cette entr\u00e9e de configuration %s. Aucun fichier journal ne sera supprim\u00e9 +###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=Le nom complet de la classe Java d\u00e9finissant le plan de stockage de mots de passe de Directory Server. En cas de changement alors que le plan de stockage de mots de passe associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce plan de stockage n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce plan de stockage de mots de passse de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du plan de stockage de mots de passe de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le fournisseur de moniteur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED_376=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que plan de stockage de mots de passe, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_PWSCHEME_EXISTS_377=Impossible d'ajouter une nouvelle entr\u00e9e de plan de stockage de mots de passe avec le DN %s car il y a d\u00e9j\u00e0 un plan de stockage enregistr\u00e9 avec ce DN -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du plug-in de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 -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 +###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=Identifiant unique pour ce backend. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne prennent pas effet tant que le backend n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que le serveur n'est pas red\u00e9marr\u00e9 -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=An error occurred that prevented the configuration backup from being properly restored. Cependant, les fichiers de la configuration d'origine qui \u00e9taient en place avant le d\u00e9but de la proc\u00e9dure de restauration ont \u00e9t\u00e9 conserv\u00e9s et se trouvent maintenant dans leur emplacement d'origine de %s -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 +###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=Une erreur a emp\u00each\u00e9 la sauvegarde de la configuration d'\u00eatre correctement restaur\u00e9e. Cependant, les fichiers de la configuration d'origine qui \u00e9taient en place avant le d\u00e9but de la proc\u00e9dure de restauration ont \u00e9t\u00e9 conserv\u00e9s et se trouvent maintenant dans leur emplacement d'origine de %s +###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=La synth\u00e8se de message calcul\u00e9e \u00e0 partir du fichier de sauvegarde correspond \u00e0 la synth\u00e8se stock\u00e9e dans les informations de sauvegarde -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 +###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=La synth\u00e8se sign\u00e9e calcul\u00e9e \u00e0 partir de la sauvegarde correspond \u00e0 la signature stock\u00e9e dans les informations de sauvegarde -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 +###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=Tous les tests effectu\u00e9s sur la sauvegarde de configuration %s du r\u00e9pertoire %s montrent que le fichier semble valide. NOTICE_CONFIG_RESTORE_SUCCESSFUL_421=La sauvegarde de configuration %s a \u00e9t\u00e9 restaur\u00e9e \u00e0 partir du fichier du r\u00e9pertoire %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=Ce fichier contient la configuration du serveur d'annuaire principal. Il ne doit pas \u00eatre \u00e9dit\u00e9 directement quand le serveur est en ligne. La configuration du serveur doit uniquement \u00eatre g\u00e9r\u00e9e au moyen des utilitaires d'administration fournis avec Directory Server -INFO_CONFIG_CORE_DESCRIPTION_ADD_MISSING_RDN_ATTRS_425=Indique si Directory Server doit ajouter automatiquement des attributs RDN manquants \u00e0 une entr\u00e9e lors de son ajout. Par d\u00e9faut, les entr\u00e9es ajout\u00e9es ne contenant pas les valeurs d'attribut RDN dans leurs listes d'attributs seront refus\u00e9es car elles violent la sp\u00e9cification de LDAP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Code de r\u00e9sultat \u00e0 utiliser pour les r\u00e9ponses auxquelles l'op\u00e9ration ne peut r\u00e9pondre du fait d'une erreur de serveur interne. La valeur doit \u00eatre le nombre entier \u00e9quivalant au code de r\u00e9sultat correspondant de LDAP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Ce fichier contient la configuration principale de Directory Server. Il ne doit pas \u00eatre \u00e9dit\u00e9 directement quand le serveur est en ligne. La configuration du serveur doit uniquement \u00eatre g\u00e9r\u00e9e au moyen des utilitaires d'administration fournis avec Directory Server +INFO_CONFIG_CORE_DESCRIPTION_ADD_MISSING_RDN_ATTRS_425=Indique si Directory Server doit ajouter automatiquement des attributs RDN manquants \u00e0 une entr\u00e9e lors de son ajout. Par d\u00e9faut, les entr\u00e9es ajout\u00e9es ne contenant pas les valeurs d'attribut RDN dans leurs listes d'attributs seront refus\u00e9es car elles violent la sp\u00e9cification de LDAP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Code de r\u00e9sultat \u00e0 utiliser pour les r\u00e9ponses auxquelles l'op\u00e9ration ne peut r\u00e9pondre du fait d'une erreur de serveur interne. La valeur doit \u00eatre le nombre entier \u00e9quivalant au code de r\u00e9sultat correspondant de LDAP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Le nom complet de la classe Java d\u00e9finissant un mappeur d'identit\u00e9 de Directory Server. En cas de changement alors que le mappeur d'identit\u00e9 associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce mappeur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce mappeur d'identit\u00e9 de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du mappeur d'identit\u00e9 de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le mappeur d'identit\u00e9es n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du mappeur d'identit\u00e9 de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le mappeur d'identit\u00e9 n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED_442=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que mappeur d'identit\u00e9, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_IDMAPPER_EXISTS_443=Impossible d'ajouter une nouvelle entr\u00e9e de mappeur d'identit\u00e9 avec le DN %s car il y a d\u00e9j\u00e0 un mappeur d'identit\u00e9 enregistr\u00e9 avec ce DN -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=DN de l'entr\u00e9e de configuration pour le mappeur d'identit\u00e9 \u00e0 utiliser par Directory Server avec le contr\u00f4le de l'authentification par proxy V2. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Nombre d'entr\u00e9es maximum par d\u00e9faut \u00e0 retourner au client pendant le traitement d'une op\u00e9ration de recherche. Il peut \u00eatre d\u00e9pass\u00e9 par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-size-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Indique si le fournisseur de synchronisation du Directory Server associ\u00e9 est activ\u00e9 et doit \u00eatre utilis\u00e9 par le serveur. Cet attribut doit \u00eatre pr\u00e9sent dans toutes les entr\u00e9es du fournisseur de synchronisation et ne pas \u00eatre modifi\u00e9 tant que Directory Server est en cours d'ex\u00e9cution -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 +###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=DN de l'entr\u00e9e de configuration pour le mappeur d'identit\u00e9 \u00e0 utiliser par Directory Server avec le contr\u00f4le de l'authentification par proxy V2. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Nombre d'entr\u00e9es maximum par d\u00e9faut \u00e0 retourner au client pendant le traitement d'une op\u00e9ration de recherche. Il peut \u00eatre ignor\u00e9 par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-size-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Indique si le fournisseur de synchronisation de Directory Server associ\u00e9 est activ\u00e9 et doit \u00eatre utilis\u00e9 par le serveur. Cet attribut doit \u00eatre pr\u00e9sent dans toutes les entr\u00e9es du fournisseur de synchronisation et ne pas \u00eatre modifi\u00e9 tant que Directory Server est en cours d'ex\u00e9cution +###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=Nom complet de la classe Java qui fournira la logique pour le fournisseur de synchronisation de Directory Server. Cet attribut doit \u00eatre pr\u00e9sent dans toutes les entr\u00e9es du fournisseur de synchronisation et ne pas \u00eatre modifi\u00e9 tant que Directory Server est en cours d'ex\u00e9cution -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 +###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=Le fournisseur de synchronisation d\u00e9fini dans l'entr\u00e9e de configuration %s est actuellement activ\u00e9, mais, selon la configuration modifi\u00e9e, il doit \u00eatre d\u00e9sactiv\u00e9. Cela ne prend pas effet tant que Directory Server n'est pas red\u00e9marr\u00e9 -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=Mode \u00e9criture pour ce backend. Cette valeur peut \u00eatre "enabled", si toutes les op\u00e9rations d'\u00e9criture sont autoris\u00e9es, "disabled", si elles sont refus\u00e9es ou bien "internal-only", si seules les op\u00e9rations d'\u00e9criture internes et les mises \u00e0 jour de synchronisation sont autoris\u00e9es. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Mode \u00e9criture pour Directory Server. La valeur peut \u00eatre "enabled", "disabled" ou "internal-only". Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Indique si les liaisons simples contenant un DN devront aussi avoir un mot de passe. En cas de d\u00e9sactivation, les liaisons sans mot de passe seront trait\u00e9es comme si elles \u00e9taient anonymes, m\u00eame si elles contiennent une liaison DN, ce qui peut cr\u00e9er une br\u00e8che dans la s\u00e9curit\u00e9 pour certains types d'applications. Lorsque cette option est activ\u00e9e, une simple requ\u00eate de liaison contenant un DN mais aucun mot de passe sera refus\u00e9e plut\u00f4t que d'avoir une authentification anonyme par d\u00e9faut. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Mode \u00e9criture pour ce backend. Cette valeur peut \u00eatre "enabled", si toutes les op\u00e9rations d'\u00e9criture sont autoris\u00e9es, "disabled", si elles sont refus\u00e9es ou bien "internal-only", si seules les op\u00e9rations d'\u00e9criture internes et les mises \u00e0 jour de synchronisation sont autoris\u00e9es. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Mode \u00e9criture pour Directory Server. La valeur peut \u00eatre "enabled", "disabled" ou "internal-only". Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Indique si les liaisons simples contenant un DN devront aussi avoir un mot de passe. En cas de d\u00e9sactivation, les liaisons sans mot de passe seront trait\u00e9es comme si elles \u00e9taient anonymes, m\u00eame si elles contiennent une liaison DN, ce qui peut cr\u00e9er une br\u00e8che dans la s\u00e9curit\u00e9 pour certains types d'applications. Lorsque cette option est activ\u00e9e, une simple requ\u00eate de liaison contenant un DN mais aucun mot de passe sera refus\u00e9e plut\u00f4t que d'avoir une authentification anonyme par d\u00e9faut. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Le nom complet de la classe Java d\u00e9finissant le valideur de mots de passe de Directory Server. En cas de changement alors que le valideur associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que celui-ci n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce valideur de mots de passe de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du valideur de mots de passe de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED_489=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que valideur de mot de passe, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_PWVALIDATOR_EXISTS_490=Impossible d'ajouter une nouvelle entr\u00e9e de valideur de mots de passe avec le DN %s car il y a d\u00e9j\u00e0 un valideur enregistr\u00e9 avec ce DN -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 +###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=Le nom complet de la classe Java d\u00e9finissant le g\u00e9n\u00e9rateur de mots de passe de Directory Server. En cas de changement alors que le g\u00e9n\u00e9rateur associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce g\u00e9n\u00e9rateur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce g\u00e9n\u00e9rateur de mots de passe de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du g\u00e9n\u00e9rateur de mots de passe de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le journal n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED_505=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que g\u00e9n\u00e9rateur de mot de passe, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_PWGENERATOR_EXISTS_506=Impossible d'ajouter une nouvelle entr\u00e9e de g\u00e9n\u00e9rateur de mots de passe avec le DN %s car il y a d\u00e9j\u00e0 un g\u00e9n\u00e9rateur enregistr\u00e9 avec ce DN -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=DN de l'entr\u00e9e de configuration d\u00e9finissant la strat\u00e9gie de mots de passe par d\u00e9faut pour Directory Server qui sera appliqu\u00e9e \u00e0 tous les utilisateurs pour lesquels une strat\u00e9gie de mots de passe personnalis\u00e9e n'a pas \u00e9t\u00e9 d\u00e9finie. Cette entr\u00e9e doit exister et sp\u00e9cifier une configuration de strat\u00e9gie de mots de passe valide. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=DN de l'entr\u00e9e de configuration d\u00e9finissant la strat\u00e9gie de mots de passe par d\u00e9faut pour Directory Server qui sera appliqu\u00e9e \u00e0 tous les utilisateurs pour lesquels une strat\u00e9gie de mots de passe personnalis\u00e9e n'a pas \u00e9t\u00e9 d\u00e9finie. Cette entr\u00e9e doit exister et sp\u00e9cifier une configuration de strat\u00e9gie de mots de passe valide. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Une entr\u00e9e de la strat\u00e9gie de mot de passe %s a \u00e9t\u00e9 supprim\u00e9e de la configuration de Directory Server. Toute entr\u00e9e d'utilisateur faisant explicitement r\u00e9f\u00e9rence \u00e0 cette strat\u00e9gie de mots de passe ne sera plus autoris\u00e9e pour l'authentification -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 +###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=Indique si le contr\u00f4le d'acc\u00e8s est activ\u00e9 et doit \u00eatre utilis\u00e9 par le serveur. Cet attribut est obligatoire -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 +###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=Le contr\u00f4le d'acc\u00e8s \u00e0 \u00e9t\u00e9 activ\u00e9 et utilisera l'impl\u00e9mentation %s -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 +###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=Nom complet de la classe Java qui fournira l'impl\u00e9mentation du contr\u00f4le d'acc\u00e8s pour Directory Server. Cet attribut est obligatoire -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=Sp\u00e9cifie un ou plusieurs DN de liaison secondaires pouvant \u00eatre utilis\u00e9s pour authentifier en tant que DN racine associ\u00e9, en plus du v\u00e9ritable DN de l'entr\u00e9e de configuration du DN racine. Les DN de liaison secondaires ne doivent pas entrer en conflit avec les DN d'autres entr\u00e9es dans le r\u00e9pertoire, ni avec d'autres DN de liaison secondaires configur\u00e9s pour d'autres DN racines. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Sp\u00e9cifie un ou plusieurs DN de liaison secondaires pouvant \u00eatre utilis\u00e9s pour authentifier en tant que DN racine associ\u00e9, en plus du v\u00e9ritable DN de l'entr\u00e9e de configuration du DN racine. Les DN de liaison secondaires ne doivent pas entrer en conflit avec les DN d'autres entr\u00e9es dans le r\u00e9pertoire, ni avec d'autres DN de liaison secondaires configur\u00e9s pour d'autres DN racines. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Le nom complet de la classe Java d\u00e9finissant le gestionnaire de notification de l'\u00e9tat du compte de Directory Server. En cas de changement alors que le gestionnaire de notification de l'\u00e9tat du compte associ\u00e9 est activ\u00e9, la modification ne prend pas effet tant que ce gestionnaire n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 -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 +###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=Indique si ce gestionnaire de notification de l'\u00e9tat du compte de Directory Server doit \u00eatre activ\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du gestionnaire de notification de l'\u00e9tat du compte de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le gestionnaire de notification n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED_558=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que gestionnaire de notification de l'\u00e9tat d'un compte, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_ACCTNOTHANDLER_EXISTS_559=Impossible d'ajouter un nouvelle entr\u00e9e de gestionnaire de notification de l'\u00e9tat du compte avec le DN %s car un gestionnaire de notification enregistr\u00e9 avec ce DN existe d\u00e9j\u00e0 -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=Nombre maximum d'entr\u00e9es candidates par d\u00e9faut o\u00f9 les correspondances sont v\u00e9rifi\u00e9es lors du traitement d'une op\u00e9ration de recherche. Il peut \u00eatre \u00e9cras\u00e9 par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-lookthrough-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Nombre maximum d'entr\u00e9es candidates par d\u00e9faut o\u00f9 les correspondances sont v\u00e9rifi\u00e9es lors du traitement d'une op\u00e9ration de recherche. Il peut \u00eatre \u00e9cras\u00e9 par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-lookthrough-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Autorisations utilis\u00e9es pour le r\u00e9pertoire contenant les fichiers de base de donn\u00e9es de backend -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=Dur\u00e9e maximum par d\u00e9faut devant \u00eatre autoris\u00e9e pour le traitement d'une op\u00e9ration de recherche. Elle peut \u00eatre d\u00e9pass\u00e9e par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-time-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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=Indique si Directory Server doit refuser les requ\u00eates provenant de clients non authentifi\u00e9s. Si cette option est "true", les clients non authentifi\u00e9s seront uniquement autoris\u00e9s \u00e0 envoyer des requ\u00eates de liaison et StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte -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 +###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=Dur\u00e9e maximum par d\u00e9faut devant \u00eatre autoris\u00e9e pour le traitement d'une op\u00e9ration de recherche. Elle peut \u00eatre d\u00e9pass\u00e9e par un utilisateur en incluant l'attribut op\u00e9rationnel ds-rlim-time-limit dans l'entr\u00e9e de l'utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Indique si Directory Server doit refuser les requ\u00eates provenant de clients non authentifi\u00e9s. Si cette option est "true", les clients non authentifi\u00e9s seront uniquement autoris\u00e9s \u00e0 envoyer des requ\u00eates de liaison et StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement +###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=Le nom complet de la classe Java d\u00e9finissant l'impl\u00e9mentation de groupe de Directory Server. En cas de changement alors que l'impl\u00e9mentation associ\u00e9e est activ\u00e9e, la modification ne prend pas effet tant que cette impl\u00e9mentation de groupe n'est pas d\u00e9sactiv\u00e9e puis r\u00e9activ\u00e9e -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 +###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=Indique si cette impl\u00e9mentation de groupe de Directory Server doit \u00eatre activ\u00e9e. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe de l'impl\u00e9mentation de groupes de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que l'impl\u00e9mentation de groupe n'est pas d\u00e9sactiv\u00e9e puis r\u00e9activ\u00e9e ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_GROUP_INITIALIZATION_FAILED_591=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant qu'impl\u00e9mentation de groupe, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_GROUP_EXISTS_592=Impossible d'ajouter une nouvelle entr\u00e9e d'impl\u00e9mentation de groupes avec le DN %s car il y a d\u00e9j\u00e0 une impl\u00e9mentation de groupes enregistr\u00e9e avec ce DN -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 +###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=Le jeu de privil\u00e8ges qui sera automatiquement assign\u00e9 aux utilisateurs root a \u00e9t\u00e9 mis \u00e0 jour. Ce nouveau jeu de privil\u00e8ges ne s'appliquera pas aux connexions existantes d\u00e9j\u00e0 authentifi\u00e9es en tant qu'utilisateur root, mais sera utilis\u00e9 pour toute authentification ult\u00e9rieure d'utilisateurs root MILD_ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES_598=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations d'ajout dans la configuration de Directory Server MILD_ERR_CONFIG_FILE_DELETE_INSUFFICIENT_PRIVILEGES_599=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations de suppression dans la configuration de Directory Server @@ -583,81 +1347,214 @@ MILD_ERR_CONFIG_FILE_MODDN_INSUFFICIENT_PRIVILEGES_601=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations de modification de DN dans la configuration de Directory Server MILD_ERR_CONFIG_FILE_SEARCH_INSUFFICIENT_PRIVILEGES_602=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations de recherche dans la configuration de Directory Server MILD_ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES_603=Vous ne disposez pas des privil\u00e8ges suffisants pour modifier le jeu de privil\u00e8ges root par d\u00e9faut -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le mappeur de certificat de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le mappeur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED_614=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que mappeur de certificat, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_CERTMAPPER_EXISTS_615=Impossible d'ajouter une nouvelle entr\u00e9e de mappeur de certificat avec le DN %s car il y a d\u00e9j\u00e0 un mappeur enregistr\u00e9 avec ce DN -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du fournisseur de gestionnaire de cl\u00e9s de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le fournisseur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED_627=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que fournisseur d'un gestionnaire cl\u00e9, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_KEYMANAGER_EXISTS_628=Impossible d'ajouter une nouvelle entr\u00e9e de fournisseur de gestionnaire de cl\u00e9s avec le DN %s car il y a d\u00e9j\u00e0 un fournisseur enregistr\u00e9 avec ce DN -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 +###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=Il est impossible d'appliquer dynamiquement la modification requise dans le nom de la classe du fournisseur de gestionnaire d'approbation de %s \u00e0 %s dans l'entr\u00e9e de configuration %s. Cette modification ne prend pas effet tant que le fournisseur n'est pas d\u00e9sactiv\u00e9 puis r\u00e9activ\u00e9 ou que Directory Server n'est pas red\u00e9marr\u00e9 MILD_ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED_640=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que fournisseur d'un gestionnaire d'approbation, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %s MILD_ERR_CONFIG_TRUSTMANAGER_EXISTS_641=Impossible d'ajouter une nouvelle entr\u00e9e de fournisseur de gestionnaire d'approbation avec le DN %s car il y a d\u00e9j\u00e0 un fournisseur enregistr\u00e9 avec ce DN -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=%s.%s a r\u00e9ussi mais a g\u00e9n\u00e9r\u00e9 les messages suivants pour l'entr\u00e9e\u00a0%s : %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 +###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=%s.%s a r\u00e9ussi mais a g\u00e9n\u00e9r\u00e9 les messages suivants pour l'entr\u00e9e\u00a0%s\u00a0: %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=Impossible de modifier une entr\u00e9e de configuration %s car la modification changerait la classe d'objet structurelle -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 +###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=La classe utilis\u00e9e pour fournir l'impl\u00e9mentation de file d'attente de Directory Server a \u00e9t\u00e9 modifi\u00e9e de %s \u00e0 %s, mais ce changement ne prend pas effet tant que le serveur n'est pas red\u00e9marr\u00e9 -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 +###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=La configuration du fournisseur de gestionnaire cl\u00e9 d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s MILD_ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLE_680=La configuration du fournisseur de gestionnaire d'approbation d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s MILD_ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLE_681=La configuration du fournisseur de gestionnaire d'approbation d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s @@ -675,29 +1572,71 @@ MILD_ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLE_694=La configuration du fournisseur d'attribut virtuel d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s MILD_ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLE_695=La configuration du gestionnaire d'alerte d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s MILD_ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILED_696=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant que gestionnaire d'alertes, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %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 +###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=Directory Server est lanc\u00e9 avec le dernier bon fichier de configuration connu %s, plut\u00f4t qu'avec le fichier de configuration actif %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 +###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=La d\u00e9finition de la propri\u00e9t\u00e9 %s Berkeley DB JE ne prend pas effet tant que le composant pour laquelle elle est d\u00e9finie n'est pas red\u00e9marr\u00e9 -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 +###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=L'\u00e9l\u00e9ment de flux de travaux %s est d\u00e9j\u00e0 enregistr\u00e9 dans Directory Server. Cet \u00e9l\u00e9ment de flux de travaux sera ignor\u00e9 -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 unstable 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 +###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=La configuration de l'extension d\u00e9finie dans l'entr\u00e9e de configuration %s n'\u00e9tait pas acceptable\u00a0: %s MILD_ERR_CONFIG_EXTENSION_INITIALIZATION_FAILED_718=Une erreur s'est produite lors de la tentative d'initialisation d'une instance de classe %s en tant qu'extension, telle qu'elle est d\u00e9finie dans l'entr\u00e9e de configuration %s\u00a0: %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_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 -- Gitblit v1.10.0