log: Switch logging to runtime when FS becomes read-only
authorRichard Phibel <rphibel@googlemail.com>
Mon, 5 Dec 2022 12:40:41 +0000 (13:40 +0100)
committerLuca Boccassi <luca.boccassi@gmail.com>
Mon, 5 Dec 2022 23:53:47 +0000 (00:53 +0100)
commit379864f89079a92ff09917e25b3aea0fadd228ac
tree77bae86735cbf287001b1c8205dddfeac4a71f7a
parenta5d63f1e2937bd62474fbb4de9d707816a1ecde7
log: Switch logging to runtime when FS becomes read-only

The journal has a mechanism to log to the runtime journal if it fails to
log to the system journal. This mechanism is not triggered when the file
system becomes read-only. We enable it here.

When appending an entry fails if shall_try_append_again returns true,
the journal is rotated. If the FS is read-only, rotation will fail and
s->system_journal will be set to NULL. After that, when find_journal
will try to open the journal since s->system_journal will be NULL, it
will open the runtime journal.
src/journal/journald-server.c