From 625f051cca398870f1d96aa78a054efabf0d77ac Mon Sep 17 00:00:00 2001 From: Chris Ridd <chris.ridd@forgerock.com> Date: Mon, 15 Jul 2013 09:09:19 +0000 Subject: [PATCH] Remove unused messages --- opends/src/messages/messages/backend.properties | 111 ------------------------------------------------------- 1 files changed, 0 insertions(+), 111 deletions(-) diff --git a/opends/src/messages/messages/backend.properties b/opends/src/messages/messages/backend.properties index 6ab978d..eb3231d 100644 --- a/opends/src/messages/messages/backend.properties +++ b/opends/src/messages/messages/backend.properties @@ -56,10 +56,6 @@ FATAL_ERR_ROOTDSE_CONFIG_ENTRY_NULL_2=An attempt was made to configure the \ root DSE backend without providing a configuration entry. This is not \ allowed -INFO_ROOTDSE_SUBORDINATE_BASE_DESCRIPTION_3=Set of base DNs \ - that will be used for singleLevel, wholeSubtree, and subordinateSubtree \ - searches based at the root DSE. If this is not provided, then the set of all \ - user-defined suffixes will be used SEVERE_WARN_ROOTDSE_NO_BACKEND_FOR_SUBORDINATE_BASE_4=Base DN "%s" is \ configured as one of the subordinate base DNs to use for searches below the \ root DSE. However, this base DN is not handled by any suffix registered with \ @@ -137,26 +133,12 @@ updated so that it will now use a new set of user-defined attributes MILD_ERR_MONITOR_GET_ENTRY_NULL_32=Unable to retrieve the requested entry \ from the monitor backend because the provided DN was null -MILD_ERR_MONITOR_BASE_TOO_DEEP_33=Unable to retrieve the requested entry %s \ - from the monitor backend because the DN is too deep. Monitor entries may not \ - be more than one level below %s MILD_ERR_MONITOR_INVALID_BASE_34=Unable to retrieve the requested entry %s \ from the monitor backend because the DN is not below the monitor base of %s -MILD_ERR_MONITOR_MULTIVALUED_RDN_35=Unable to retrieve the requested entry %s \ - from the monitor backend because monitor entries may not contain multivalued \ - RDNs -MILD_ERR_MONITOR_NO_SUCH_PROVIDER_36=Unable to retrieve the requested entry \ - from the monitor backend because there is no monitor provider "%s" registered \ - with the Directory Server INFO_MONITOR_UPTIME_37=%d days %d hours %d minutes %d seconds SEVERE_ERR_SCHEMA_CONFIG_ENTRY_NULL_38=An attempt was made to configure the \ schema backend without providing a configuration entry. This is not allowed, \ and no schema information will be available over protocol -INFO_SCHEMA_DESCRIPTION_ENTRY_DN_39=DN or set of DNs for the \ - entries that may be retrieved in order to retrieve the Directory Server \ - schema information. Multiple values may be provided if the schema is to be \ - available in multiple locations for compatibility purposes. If no value is \ - provided, a default of "cn=schema" will be used SEVERE_ERR_SCHEMA_CANNOT_DETERMINE_BASE_DN_40=An error occurred while trying \ to determine the base DNs to use when publishing the Directory Server schema \ information, as specified in the ds-cfg-schema-entry-dn attribute of \ @@ -166,18 +148,10 @@ operations are not supported in the schema backend MILD_ERR_SCHEMA_DELETE_NOT_SUPPORTED_42=Unwilling to remove entry "%s" \ because delete operations are not supported in the schema backend -MILD_ERR_SCHEMA_MODIFY_NOT_SUPPORTED_43=Unwilling to update entry "%s" \ - because modify operations are not yet supported in the schema backend. If \ - you wish to alter the contents of the base schema entry itself, then it may \ - be possible to do so by modifying the "%s" entry in the configuration MILD_ERR_SCHEMA_MODIFY_DN_NOT_SUPPORTED_44=Unwilling to rename entry "%s" \ because modify DN operations are not supported in the schema backend SEVERE_ERR_SCHEMA_UNABLE_TO_EXPORT_BASE_45=An error occurred while attempting \ to export the base schema entry: %s -SEVERE_ERR_SCHEMA_IMPORT_NOT_SUPPORTED_46=The schema backend does not support \ - LDIF import operations -SEVERE_ERR_SCHEMA_BACKUP_AND_RESTORE_NOT_SUPPORTED_47=The schema backend does \ - not yet provide a facility for backup and restore operations MILD_ERR_SCHEMA_INVALID_BASE_48=Unable to retrieve the requested entry %s \ from the schema backend because the DN is equal to one of the schema entry \ DNs @@ -340,8 +314,6 @@ SEVERE_ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNAL_110=An error occurred \ while attempting to perform internal initialization on an instance of class \ %s with the information contained in the provided entry: %s -SEVERE_ERR_TASKBE_CONFIG_ENTRY_NULL_111=The configuration entry provided when \ - attempting to initialize the task backend was null SEVERE_ERR_TASKBE_NO_BASE_DNS_112=The task backend configuration entry does \ not contain any base DNs. There must be exactly one base DN for task \ information in the Directory Server @@ -352,22 +324,6 @@ while attempting to decode recurring task base %s as a DN: %s SEVERE_ERR_TASKBE_CANNOT_DECODE_SCHEDULED_TASK_BASE_DN_115=An error occurred \ while attempting to decode scheduled task base %s as a DN: %s -INFO_TASKBE_DESCRIPTION_RETENTION_TIME_116=Length of time in \ - seconds that task information should be retained after processing on that \ - task has completed. Once this period has passed, the task information will \ - be automatically removed to conserve memory and disk space -SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_RETENTION_TIME_117=An unexpected error \ - occurred while attempting to initialize the task retention time \ - configuration: %s -INFO_TASKBE_DESCRIPTION_BACKING_FILE_118=Path to the backing \ - file for the task backend. This LDIF file will hold all the configuration \ - for the defined scheduled tasks and recurring tasks -SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_BACKING_FILE_119=An unexpected error \ - occurred while attempting to initialize the task backing file configuration: \ - %s -SEVERE_ERR_TASKBE_NO_BACKING_FILE_120=The updated configuration entry does \ - not have a value for the required %s attribute, which specifies the path to \ - the task data backing file SEVERE_ERR_TASKBE_BACKING_FILE_EXISTS_121=The specified task data backing \ file %s already exists and the Directory Server will not attempt to overwrite \ it. Please delete or rename the existing file before attempting to use that \ @@ -384,12 +340,6 @@ Please choose a new path for the task data backing file SEVERE_ERR_TASKBE_ERROR_GETTING_BACKING_FILE_125=An error occurred while \ attempting to determine the new path to the task data backing file: %s -SEVERE_ERR_TASKBE_NO_RETENTION_TIME_126=The updated configuration entry does \ - not have a value for the required %s attribute, which specifies the length of \ - time in seconds that information about completed tasks should be retained \ - before they are cleaned up -SEVERE_ERR_TASKBE_ERROR_GETTING_RETENTION_TIME_127=An error occurred while \ - attempting to determine the completed task retention time: %s INFO_TASKBE_UPDATED_RETENTION_TIME_128=The completed task retention time has \ been updated to %d seconds. This will take effect immediately INFO_TASKBE_UPDATED_BACKING_FILE_129=The path to the task data backing file \ @@ -474,20 +424,8 @@ SEVERE_ERR_TASKBE_IMPORT_NOT_SUPPORTED_155=The task backend does not support \ LDIF import operations INFO_TASKBE_INTERRUPTED_BY_SHUTDOWN_156=The tasks backend is being shut down -INFO_ROOTDSE_DESCRIPTION_SHOW_ALL_ATTRIBUTES_157=Indicates whether all \ - attributes in the root DSE should be treated like user attributes (and \ - therefore returned to clients by default) regardless of the Directory Server \ - schema configuration -SEVERE_ERR_ROOTDSE_CANNOT_DETERMINE_ALL_USER_ATTRIBUTES_158=An error occurred \ - while trying to determine the value of the %s configuration attribute, which \ - controls whether to treat all root DSE attributes like user attributes: %s. \ - The attributes in the root DSE will be treated based on their definition in \ - the server schema INFO_ROOTDSE_UPDATED_SHOW_ALL_ATTRS_159=The root DSE configuration has been \ updated so that configuration attribute %s will now use a value of %s -SEVERE_ERR_TASKSCHED_REMOVE_RECURRING_EXISTING_ITERATION_160=Unable to remove \ - recurring task %s because there is already a scheduled iteration of that task \ - with ID %s that must be removed first SEVERE_ERR_TASKSCHED_REMOVE_PENDING_NO_SUCH_TASK_161=Unable to remove pending \ task %s because no such task exists SEVERE_ERR_TASKSCHED_REMOVE_PENDING_NOT_PENDING_162=Unable to remove pending \ @@ -518,14 +456,6 @@ SEVERE_ERR_BACKUP_CANNOT_DECODE_BACKUP_ROOT_DN_172=Unable to initialize the \ backup backend because an error occurred while attempting to decode the base \ DN for the backend: %s -INFO_BACKUP_DESCRIPTION_BACKUP_DIR_LIST_173=Set of directories \ - that will be accessed by default for search operations in the backup backend. \ - Backup directories not in this list may still be accessed by directly \ - specifying the backup directory in the search base DN. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_BACKUP_CANNOT_DETERMINE_BACKUP_DIR_LIST_174=An error occurred \ - while attempting to determine the backup directory list: %s. Initialization \ - of the backup backend cannot continue SEVERE_ERR_BACKUP_GET_ENTRY_NULL_175=Unable to retrieve an entry from the \ backup backend because the requested entry was null SEVERE_ERR_BACKUP_INVALID_BASE_176=Requested entry %s does not exist in the \ @@ -576,8 +506,6 @@ the memory-based backend SEVERE_ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDREN_197=Cannot delete \ entry %s because it has one or more subordinate entries -SEVERE_ERR_MEMORYBACKEND_MODDN_NOT_SUPPORTED_198=Modify DN operations are not \ - supported in the memory-based backend SEVERE_ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_WRITER_199=Unable to create an \ LDIF writer: %s SEVERE_ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIF_200=Cannot write entry %s \ @@ -596,23 +524,8 @@ entry %s because the target entry is in a different backend SEVERE_ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXIST_207=Cannot rename entry \ %s because the new parent entry %s doesn't exist -INFO_SCHEMA_DESCRIPTION_SHOW_ALL_ATTRIBUTES_208=Indicates whether to treat \ - attributes in the subschema entry as user attributes even if they are marked \ - operational. This may provide compatibility with some applications that \ - expect schema attributes like attributeType and objectClasses to be included \ - by default even if they are not requested. Note that the ldapSyntaxes \ - attribute will always be treated as operational in order to avoid problems \ - with attempts to modify the schema over protocol -SEVERE_ERR_SCHEMA_CANNOT_DETERMINE_SHOW_ALL_209=An error occurred while \ - trying to determine whether to treat all subschema entry attributes as user \ - attributes regardless of the way they are defined in the schema, as specified \ - in the ds-cfg-show-all-attributes attribute of configuration entry %s: %s. \ - The default behavior, which is to treat the attribute types as defined in the \ - server schema, will be used FATAL_ERR_BACKEND_CANNOT_REGISTER_BASEDN_210=An error occurred while \ attempting to register base DN %s in the Directory Server: %s -MILD_ERR_SCHEMA_DELETE_MODTYPE_NOT_SUPPORTED_211=The schema backend does not \ - currently support removing existing schema elements MILD_ERR_SCHEMA_INVALID_MODIFICATION_TYPE_212=The schema backend does not \ support the %s modification type MILD_ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPE_213=The schema backend does \ @@ -621,9 +534,6 @@ matching rule uses may be modified MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_ATTRTYPE_214=An error occurred while \ attempting to decode the attribute type "%s": %s -MILD_ERR_SCHEMA_MODIFY_ATTRTYPE_ALREADY_EXISTS_215=Unable to add attribute \ - type %s to the server schema because there is an existing attribute type \ - with a conflicting name or OID: %s MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_OBJECTCLASS_216=An error occurred while \ attempting to decode the object class "%s": %s MILD_ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_OBJECTCLASS_217=Unable to add \ @@ -635,11 +545,6 @@ MILD_ERR_SCHEMA_MODIFY_OC_UNDEFINED_OPTIONAL_ATTR_219=Unable to add \ objectclass %s because it allows attribute %s which is not defined in the \ server schema -MILD_ERR_SCHEMA_MODIFY_OBJECTCLASS_ALREADY_EXISTS_220=Unable to add \ - objectclass %s to the server schema because there is an existing objectclass \ - with a conflicting name or OID: %s -MILD_ERR_SCHEMA_MODIFY_CANNOT_READ_EXISTING_USER_SCHEMA_221=An error occurred \ - while attempting to read the contents of schema file %s: %s MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA_222=An error occurred while \ attempting to write the updated schema: %s MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_NAME_FORM_223=An error occurred while \ @@ -788,9 +693,6 @@ MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_STRUCTURAL_272=Unable to add DIT content \ rule %s because it references structural objectclass %s which is defined in \ the server schema but is not structural -MILD_ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_NF_273=Unable to add \ - name form %s because it references structural objectclass %s which is already \ - associated with another name form %s MILD_ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_ATTRIBUTE_TYPE_274=Unable to add \ attribute type %s because the superior type %s is marked as OBSOLETE in the \ server schema @@ -820,9 +722,6 @@ MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_AUXILIARY_283=Unable to add DIT content \ rule %s because it references auxiliary object class %s which is defined in \ the server schema but is not an auxiliary class -MILD_ERR_SCHEMA_MODIFY_DCR_AUXILIARY_OC_OBSOLETE_284=Unable to add DIT \ - content rule %s because it allows auxiliary object class %s which is marked \ - as OBSOLETE in the server schema MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_REQUIRED_ATTR_285=Unable to add DIT \ content rule %s because it requires attribute type %s which is marked as \ OBSOLETE in the server schema @@ -923,8 +822,6 @@ generate a self-signed certificate %s in the trust store file %s: %s SEVERE_ERR_TRUSTSTORE_CANNOT_ADD_CERT_321=Error while trying to add \ certificate %s to the trust store file %s: %s -SEVERE_ERR_TRUSTSTORE_DELETE_NOT_SUPPORTED_322=Delete operations are not \ - supported in the trust store backend SEVERE_ERR_TRUSTSTORE_ENTRY_MISSING_CERT_ATTR_323=The entry %s could not be \ added because it does not contain a certificate attribute %s SEVERE_ERR_TRUSTSTORE_ENTRY_HAS_MULTIPLE_CERT_ATTRS_324=The entry %s could \ @@ -963,12 +860,6 @@ SEVERE_ERR_LDIF_BACKEND_MULTIPLE_BASE_DNS_339=The LDIF backend defined in \ configuration entry %s only supports a single base DN, but was configured \ for use with multiple base DNs -SEVERE_ERR_LDIF_BACKEND_ERROR_OPENING_FILE_340=An error occurred while \ - attempting to open LDIF file %s for use by the LDIF backend defined in \ - configuration entry %s: %s -SEVERE_ERR_LDIF_BACKEND_ERROR_READING_ENTRY_341=An error occurred while \ - attempting to read data from LDIF file %s into the LDIF backend defined in \ - configuration entry %s: %s MILD_ERR_LDIF_BACKEND_DUPLICATE_ENTRY_342=LDIF file %s configured for use \ with the LDIF backend defined in configuration entry %s has multiple entries \ with a DN of %s @@ -1016,8 +907,6 @@ MILD_ERR_LDIF_BACKEND_BACKUP_RESTORE_NOT_SUPPORTED_361=The LDIF backend \ currently does not provide a backup or restore mechanism. Use LDIF import \ and export operations instead -MILD_ERR_LDIF_BACKEND_LDIF_DOESNT_EXIST_362=LDIF file %s referenced in LDIF \ - backend configuration entry %s does not exist INFO_LDIF_BACKEND_LDIF_FILE_CHANGED_363=The change to the LDIF file path \ will not take effect until the backend is disabled and re-enabled INFO_LDIF_BACKEND_BASE_DN_CHANGED_364=The change to the LDIF backend base DN \ -- Gitblit v1.10.0