chiark / gitweb /
execute: increase severity of journal connect failure message
authorMichal Schmidt <mschmidt@redhat.com>
Fri, 15 Feb 2013 23:34:12 +0000 (00:34 +0100)
committerMichal Schmidt <mschmidt@redhat.com>
Sat, 16 Feb 2013 00:18:08 +0000 (01:18 +0100)
journald is supposed to work. Failure to connect to its socket implies
losing messages. It should be a very unusual event. Log the failure with
LOG_CRIT.

Just because this unit's stdout/stderr failed to connect to the journal
does not necessarily mean that we shouldn't try to log the failure using
a structured entry, so let's use log_struct_unit.


No differences found