summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorVito Caputo <vcaputo@gnugeneration.com>2016-08-25 08:37:57 -0700
committerLennart Poettering <lennart@poettering.net>2016-08-25 17:37:57 +0200
commit929eeb5498e8ae87e05ae683c6d3014d4b59056d (patch)
tree57a8594ebd639289555e079416988f4b8a1adf31 /tools
parent1ef72b55ba6d38f879d7ac9f0237cf8a2b53f0e6 (diff)
journal: implicitly flush to var on recovery (#4028)
When the system journal becomes re-opened post-flush with the runtime journal open, it implies we've recovered from something like an ENOSPC situation where the system journal rotate had failed, leaving the system journal closed, causing the runtime journal to be opened post-flush. For the duration of the unavailable system journal, we log to the runtime journal. But when the system journal gets opened (space made available, for example), we need to close the runtime journal before new journal writes will go to the system journal. Calling server_flush_to_var() after opening the system journal with a runtime journal present, post-flush, achieves this while preserving the runtime journal's contents in the system journal. The combination of the present flushed flag file and the runtime journal being open is a state where we should be logging to the system journal, so it's appropriate to resume doing so once we've successfully opened the system journal.
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions