There are a whole lot more complaints than that for journald. The most common one (and one I share) is how slow it can be. `systemctl status foo.service` take

There are a whole lot more complaints than that for journald. The most common one (and one I share) is how slow it can be. `systemctl status foo.service` takes a significant amount of time on any of my machines thanks to the journal, and that's just the reader side. It used to be quite crashy with lots of CPU overhead, but that has improved over time, the metadata caching helped a bunch with the overhead. There was also a pretty embarrassing CVE not long ago: https://nvd.nist.gov/vuln/detail/CVE-2018-16865 https://nvd.nist.gov/vuln/detail/CVE-2018-16865