> @xnox > "The journald daemon has limits set for logs, meaning they will be > rotated and discarded and should not cause out of disk-space errors." > > What are they? AFAICT it only has limits on the number of files, but > not how big they can overall become.
The limits are documented in `man journald.conf`. One of them is " SystemMaxUse=, ", which is based on disk usage, not file size. > I'm also thinking that the duplicate writing of logs could cause other > regressions, one example being where high disk throughput is ongoing and > many things being written to the logs. Thoughts? Additional disk writing is somewhat mitigated by the general increase in disk performance over time in new hardware As one user found here, SSD is about 5x faster than HDD and the newer NVMe SSDs are about 5x faster than the older SSDs. A new NVMe SSD is about 25x faster than an HDD. https://photographylife.com/nvme-vs-ssd-vs-hdd-performance The idea here is to be "safe by default". People are welcome to prioritize performance and reduce logging beyond the defaults. Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
