|
|
@@ -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...
|
JINMEI Tatuya