|
@@ -28,23 +28,23 @@ destination should be one of "console", "file", or "syslog".
|
|
|
|
|
|
% LOG_BAD_SEVERITY unrecognized log severity: %1
|
|
|
A logger severity value was given that was not recognized. The severity
|
|
|
-should be one of "DEBUG", "INFO", "WARN", "ERROR", or "FATAL".
|
|
|
+should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE".
|
|
|
|
|
|
% LOG_BAD_STREAM bad log console output stream: %1
|
|
|
-A log console output stream was given that was not recognized. The output
|
|
|
-stream should be one of "stdout", or "stderr"
|
|
|
+Logging has been configured so that output is written to the terminal
|
|
|
+(console) but the stream on which it is to be written is not recognised.
|
|
|
+Allowed values are "stdout" and "stderr"
|
|
|
|
|
|
% LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code
|
|
|
-During start-up, BIND10 detected that the given message identification had
|
|
|
-been defined multiple times in the BIND10 code.
|
|
|
-
|
|
|
-This has no ill-effects other than the possibility that an erronous
|
|
|
-message may be logged. However, as it is indicative of a programming
|
|
|
-error, please log a bug report.
|
|
|
+During start-up, BIND10 detected that the given message identification
|
|
|
+had been defined multiple times in the BIND10 code. This indicates a
|
|
|
+programming error; please log a bug report.
|
|
|
|
|
|
% LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found
|
|
|
When reading a message file, more than one $NAMESPACE directive was found.
|
|
|
-Such a condition is regarded as an error and the read will be abandoned.
|
|
|
+(This directive is used to set a C++ namespace when generating header
|
|
|
+files during software development.) Such a condition is regarded as an
|
|
|
+error and the read will be abandoned.
|
|
|
|
|
|
% LOG_INPUT_OPEN_FAIL unable to open message file %1 for input: %2
|
|
|
The program was not able to open the specified input message file for
|