summaryrefslogtreecommitdiff
path: root/src/core/mount.c
diff options
context:
space:
mode:
authorMichal Schmidt <mschmidt@redhat.com>2013-02-16 00:34:12 +0100
committerMichal Schmidt <mschmidt@redhat.com>2013-02-16 01:18:08 +0100
commit80cbda3558c534b575bf5315fa53b0f82dc088ab (patch)
treef52ab390ad5a95d4978c2a5dd43676a36c9c66d8 /src/core/mount.c
parenteb17e935988993f4e0ebe08be81150ce35b140bf (diff)
execute: increase severity of journal connect failure message
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.
Diffstat (limited to 'src/core/mount.c')
0 files changed, 0 insertions, 0 deletions