systemd/catalog
Luca Boccassi a0cca4d1b0 portable: log structured message when attach/detach succeeds
Currently portabled is completely silent (when not using debug level). But
when the system state is changed (ie: a portable is attached or detached)
there are no traces left in the journal. Log at info level when either of
those operations succeed, as they are effectively changing the state of
the system.

Create new MESSAGE_IDs for these logs, and also append PORTABLE_ROOT=
(and PORTABLE_EXTENSION= if any), like the units themselves are
configured to do via LogExtraFields=, so that the same metadata can
be found in the attach/detach messages and in logs from the units
themselves.
2024-01-19 17:03:04 +01:00
..
meson.build meson: use 'sh' variable everywhere 2023-08-24 11:17:50 +02:00
systemd.be.catalog.in
systemd.be@latin.catalog.in
systemd.bg.catalog.in Drop split-usr and unmerged-usr support 2023-07-28 19:34:03 +01:00
systemd.catalog.in portable: log structured message when attach/detach succeeds 2024-01-19 17:03:04 +01:00
systemd.da.catalog.in
systemd.de.catalog.in Move message repeat 2022-06-01 00:20:30 +09:00
systemd.fr.catalog.in Drop split-usr and unmerged-usr support 2023-07-28 19:34:03 +01:00
systemd.hr.catalog.in
systemd.hu.catalog.in
systemd.it.catalog.in Drop split-usr and unmerged-usr support 2023-07-28 19:34:03 +01:00
systemd.ko.catalog.in
systemd.pl.catalog.in Drop split-usr and unmerged-usr support 2023-07-28 19:34:03 +01:00
systemd.pt_BR.catalog.in
systemd.ru.catalog.in Drop split-usr and unmerged-usr support 2023-07-28 19:34:03 +01:00
systemd.sr.catalog.in
systemd.zh_CN.catalog.in
systemd.zh_TW.catalog.in