4 ms·

Jesus. From the first bug mentioned in your comment in that thread: Reporter: "libsystemd-journal or systemd-journald loses some systemd's parts of message con

• andor 11y ago
  Software Development Jesus descends from the clouds, wearing a virtual reality headset and a t-shirt with the words "freedesktop.org". Something about him reminds you of Bill Gates, but you are not sure what, the headset with its peculiar red laser pointer attached to the side covers too much of his face. He opens his right palm towards your computer, which surprisingly seems to be running Fedora Linux now, and through the magic of Zeroconf networking and D-Bus, the following text appears on your screen: Happy to explain this to you, simoncion! After receiving a log message from a client process, the journal tries to get trusted metadata, like the application name, about that process. If the application exits too soon after logging its message, some of that metadata, e.g. /proc/<pid>/cmdline, might not be available anymore. The message itself is always logged, though. Syslog, of course, also logs application names, but that information cannot be trusted, because it is reported by the clients themselves. So even if not all expected metadata is logged, you lose nothing compared to syslog.