BIND 10 trac758, updated. e3ef2529a0582f0b146ea7326cf2d52312149cf9 [trac758] fixed misspellings
BIND 10 source code commits
bind10-changes at lists.isc.org
Fri Jul 1 00:44:35 UTC 2011
The branch, trac758 has been updated
via e3ef2529a0582f0b146ea7326cf2d52312149cf9 (commit)
from 348387b8fa68c25873b4ee50881738c9c0e83670 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e3ef2529a0582f0b146ea7326cf2d52312149cf9
Author: JINMEI Tatuya <jinmei at isc.org>
Date: Thu Jun 30 17:43:51 2011 -0700
[trac758] fixed misspellings
-----------------------------------------------------------------------
Summary of changes:
src/bin/bind10/bind10_messages.mes | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
-----------------------------------------------------------------------
diff --git a/src/bin/bind10/bind10_messages.mes b/src/bin/bind10/bind10_messages.mes
index 8bf8269..b6604a0 100644
--- a/src/bin/bind10/bind10_messages.mes
+++ b/src/bin/bind10/bind10_messages.mes
@@ -29,7 +29,7 @@ This message shows whether or not the resolver should be
started according to the configuration.
% BIND10_INVALID_USER invalid user: '%1'
-The boss process was started with the -u option, to drop root priveleges
+The boss process was started with the -u option, to drop root privileges
and continue running as the specified user, but the user is unknown.
% BIND10_KILL_PROCESS killing process %1
@@ -54,7 +54,7 @@ leave the system in an inconsistent state. BIND10 will now shut down
% BIND10_MSGQ_DISAPPEARED msgq channel disappeared
While listening on the message bus channel for messages, it suddenly
disappeared. The msgq daemon may have died. This might lead to an
-inconsistend state of the system, and BIND 10 will now shut down.
+inconsistent state of the system, and BIND 10 will now shut down.
% BIND10_PROCESS_ENDED_NO_EXIT_STATUS process %1 (PID %2) died: exit status not available
The given process ended unexpectedly, but no exit status is
@@ -89,7 +89,7 @@ it now. The new configuration is printed.
The boss module received the given signal.
% BIND10_RESURRECTED_PROCESS resurrected %1 (PID %2)
-The given process has been restarted succesfully, and is now running
+The given process has been restarted successfully, and is now running
with the given process id.
% BIND10_RESURRECTING_PROCESS resurrecting dead %1 process...
More information about the bind10-changes
mailing list