]> git.ipfire.org Git - thirdparty/plymouth.git/commit
kmsg-reader: Seek to the end of the ringbuffer dmesg-replay
authorAdrian Vovk <adrianvovk@gmail.com>
Fri, 9 May 2025 19:35:38 +0000 (15:35 -0400)
committerAdrian Vovk <adrianvovk@gmail.com>
Mon, 12 May 2025 20:05:43 +0000 (16:05 -0400)
commita53065d0ce0b28a214b9088afc9d4d769c030d3b
tree4b9252ce6afc2d4db3bac9223af32dd555f0f7c4
parent6d7b3c3342e80f94410165c72bb2d907624e3fff
kmsg-reader: Seek to the end of the ringbuffer

Otherwise, whenever plymouth starts we'd replay all previous kmsg
entries, even if they've already been logged to the console. This leads
to duplicated log entires, and makes it hard to debug things.

With /dev/console, we only log what we capture while Plymouth is
running. Let's do the same with /dev/kmsg
src/libply-splash-core/ply-kmsg-reader.c