From ef6399f38704fbaff1b195ab896a03fbb733b951 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Mon, 28 Aug 2017 20:41:00 +0200 Subject: Use 'fatal:' instead of 'error:' for hard failures in agent --- bbot/diagnostics.cxx | 2 +- bbot/diagnostics.hxx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bbot/diagnostics.cxx b/bbot/diagnostics.cxx index b5bd9f8..7ba84c2 100644 --- a/bbot/diagnostics.cxx +++ b/bbot/diagnostics.cxx @@ -68,7 +68,7 @@ namespace bbot // We don't always see colorized output so keep 'error: ', etc. // - fail.type_ = with_critical ? "<2>error: " : "<3>error: "; + fail.type_ = with_critical ? "<2>fatal: " : "<3>error: "; error.type_ = "<3>error: "; warn.type_ = "<4>warning: "; info.type_ = "<6>"; diff --git a/bbot/diagnostics.hxx b/bbot/diagnostics.hxx index 1e349ec..99d3df4 100644 --- a/bbot/diagnostics.hxx +++ b/bbot/diagnostics.hxx @@ -181,7 +181,7 @@ namespace bbot // If with_critical is true, then distinguish between fail (critical error, // daemon terminates) and error (non-fatal error, daemon continues to run). // Note that this means we should be careful not to use fail to report - // normal errors and vice-versa. + // normal errors and vice-versa (see fail hard). // void systemd_diagnostics (bool with_critical); -- cgit v1.1