924426a703
systemd-journal-remote always wrote the boot-id of the device it was running on to the header of its journal files. When the source had a different boot-id (because it was generated on a different boot, or a different device), the boot-ids in the file were inconsistent. The _BOOT_ID field was that of the source, but the journal file header and each entry object header were that of the device systemd-journal-remote ran on. This breaks journalctl --list-boots on any of these files. Set the boot-id in the header to be that of the source. This also fixes the entry object headers. |
||
---|---|---|
.. | ||
browse.html | ||
journal-gatewayd.c | ||
journal-remote-main.c | ||
journal-remote-parse.c | ||
journal-remote-parse.h | ||
journal-remote-write.c | ||
journal-remote-write.h | ||
journal-remote.c | ||
journal-remote.conf.in | ||
journal-remote.h | ||
journal-upload-journal.c | ||
journal-upload.c | ||
journal-upload.conf.in | ||
journal-upload.h | ||
log-generator.py | ||
meson.build | ||
microhttpd-util.c | ||
microhttpd-util.h |