Commit 6160ff53 authored by Jeremy C. Reed's avatar Jeremy C. Reed
Browse files

[master] fixed typos and misspellings in .mes message files

parent 580b893a
......@@ -177,7 +177,7 @@ The separate thread for maintaining data source clients has been stopped.
% AUTH_DATASRC_CLIENTS_BUILDER_WAKE_ERR failed to wake up main thread: %1
A low-level error happened when trying to send data to the main thread to wake
it up. Terminating to prevent inconsistent state and possiblu hang ups.
it up. Terminating to prevent inconsistent state and possible hang ups.
% AUTH_DATASRC_CLIENTS_SHUTDOWN_ERROR error on waiting for data source builder thread: %1
This indicates that the separate thread for maintaining data source
......
......@@ -29,7 +29,7 @@ The named component failed previously and we will try to restart it to provide
as flawless service as possible, but it should be investigated what happened,
as it could happen again.
% BIND10_COMPONENT_SHUTDOWN_ERROR An error occured stopping component %1
% BIND10_COMPONENT_SHUTDOWN_ERROR An error occurred stopping component %1
An attempt to gracefully shutdown a component failed.
% BIND10_COMPONENT_START component %1 is starting
......
......@@ -146,7 +146,7 @@ a brief service interruption.
A warning message indicating that a client is attempting to extend lease lifetime
for the address, but the server does not have any information about the subnet this
client belongs to. This may mean that faulty the mobile client changed its location
and is trying to renew its old address (client is supposed to send confirm, not rewew
and is trying to renew its old address (client is supposed to send confirm, not renew
in such cases, according to RFC3315) or the server configuration has changed and
information about existing subnet was removed. Note that in a sense this is worse
case of DHCP6_EXTEND_NA_UNKNOWN, as not only the lease is unknown, but also the subnet
......@@ -490,7 +490,7 @@ reconfiguration procedure.
% DHCP6_SERVERID_WRITE_FAIL server was not able to write its ID to file %1
This warning message indicates that server was not able to write its
server identifier (DUID) to a file. This likely indicates lack of write
permission to a given file or directory. This is not cricital and the
permission to a given file or directory. This is not critical and the
server will continue to operate, but server will generate different DUID
during every start and clients will need to go through a rebind phase
to recover.
......
......@@ -22,7 +22,7 @@ The cause of the error is included in the message. None of the received
updates applied, and the daemon keeps running with the previous configuration.
% MEMMGR_CONFIG_UPDATE received new configuration
A debug message. The memmgr daemon receives configuratiopn updates
A debug message. The memmgr daemon receives configuration updates
and is now applying them to its running configurations.
% MEMMGR_DATASRC_CONFIG_ERROR failed to update data source configuration: %1
......
......@@ -22,7 +22,7 @@ This is an error message issued when an error occurs while unloading the
UserCheckHook library. This is unlikely to occur and normal operations of the
library will likely resume when it is next loaded.
% USER_CHK_SUBNET4_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet4_select callout: %1
% USER_CHK_SUBNET4_SELECT_ERROR DHCP UserCheckHook an unexpected error occurred in subnet4_select callout: %1
This is an error message issued when the DHCP UserCheckHook subnet4_select hook
encounters an unexpected error. The message should contain a more detailed
explanation.
......@@ -32,7 +32,7 @@ This is an error message issued when the DHCP UserCheckHook subnet4_select hook
has been invoked but the UserRegistry has not been created. This is a
programmatic error and should not occur.
% USER_CHK_SUBNET6_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet6_select callout: %1
% USER_CHK_SUBNET6_SELECT_ERROR DHCP UserCheckHook an unexpected error occurred in subnet6_select callout: %1
This is an error message issued when the DHCP UserCheckHook subnet6_select hook
encounters an unexpected error. The message should contain a more detailed
explanation.
......
......@@ -65,7 +65,7 @@ included in the log message. The server still keeps accepting new
connections, so unless it happens often it's probably okay to ignore
this error. If the shown error indicates something like "too many
open files", it's probably because the run time environment is too
restrictive on this limitation, so consider adjusing the limit using
restrictive on this limitation, so consider adjusting the limit using
a tool such as ulimit. If you see other types of errors too often,
there may be something overlooked; please file a bug report in that case.
......
......@@ -19,7 +19,7 @@ $NAMESPACE isc::datasrc
% DATASRC_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'
The software refuses to load NSEC3 records into a wildcard domain or
the owner name has two or more labels below the zone origin.
It isn't explicitly forbidden, but no sane zone wouldn have such names
It isn't explicitly forbidden, but no sane zone would have such names
for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is
compatible with BIND 9.
......
......@@ -23,7 +23,7 @@ by providing everything found inside the domain.
% DATASRC_MEMORY_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'
The software refuses to load NSEC3 records into a wildcard domain or
the owner name has two or more labels below the zone origin.
It isn't explicitly forbidden, but no sane zone wouldn have such names
It isn't explicitly forbidden, but no sane zone would have such names
for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is
compatible with BIND 9.
......
......@@ -418,7 +418,7 @@ V6) is about to open a PostgreSQL lease database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
% DHCPSRV_PGSQL_DEALLOC_ERROR An error occured deallocating SQL statements while closing the PostgreSQL lease database: %1
% DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
This is an error message issued when a DHCP server (either V4 or V6) experienced
and error freeing database SQL resources as part of closing its connection to
the Postgresql database. The connection is closed as part of normal server
......
......@@ -63,7 +63,7 @@ restart BIND 10.
% HOOKS_HOOK_LIST_RESET the list of hooks has been reset
This is a message indicating that the list of hooks has been reset.
While this is usual when running the BIND 10 test suite, it should not be
seen when running BIND 10 in a producion environment. If this appears,
seen when running BIND 10 in a production environment. If this appears,
please report a bug through the usual channels.
% HOOKS_INCORRECT_VERSION hook library %1 is at version %2, require version %3
......
......@@ -30,6 +30,6 @@ The MemorySegmentBuilder failed to load the specified zone when handling
the load command. This zone will be skipped.
% LIBMEMMGR_BUILDER_ZONE_WRITER_LOAD_2_ERROR Error loading zone '%1', data source '%2': '%3'
An exception occured when the MemorySegmentBuilder tried to load the
An exception occurred when the MemorySegmentBuilder tried to load the
specified zone when handling the load command. This zone will be
skipped.
......@@ -55,7 +55,7 @@ the one we sent. Since there was a response, no more notifies will
be sent to this server for this notification event.
% NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1
The notify_out library sent a notify message to the namesever at the
The notify_out library sent a notify message to the nameserver at the
given address, but the reply did not have the QR bit set to one.
Since there was a response, no more notifies will be sent to this
server for this notification event.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment