|
|
@@ -56,7 +56,7 @@ 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.
|
|
|
|
|
|
-% BIND10_PROCESS_ENDED_NO_EXIT_STATUS Process %1 (PID %2) died: exit status not available
|
|
|
+% 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
|
|
|
available. Depending on which module it was, it may simply be
|
|
|
restarted, or it may be a problem that will cause the boss module to
|
|
|
@@ -65,7 +65,7 @@ which, if it has died suddenly, may leave the system in an
|
|
|
inconsistent state. BIND10 will also shut down now if it has been run
|
|
|
with --brittle.
|
|
|
|
|
|
-% BIND10_PROCESS_ENDED_WITH_EXIT_STATUS Process %1 (PID %2) terminated, exit status = %3
|
|
|
+% BIND10_PROCESS_ENDED_WITH_EXIT_STATUS process %1 (PID %2) terminated, exit status = %3
|
|
|
The given process ended unexpectedly with the given exit status.
|
|
|
Depending on which module it was, it may simply be restarted, or it
|
|
|
may be a problem that will cause the boss module to shut down too.
|
Jelte Jansen