5mo ago

Remember to not to forget clearing your journal

You're viewing a single thread.

62 comments

Fucking blows my mind that journald broke what is essentially the default behavior of every distro's use of logrotate and no one bats an eye.
- I'm not sure if you're joking or not, but the behavior of journald is fairly dynamic and can be configured to an obnoxious degree, including compression and sealing.
  By default, the size limit is 4GB:
  SystemMaxUse= and RuntimeMaxUse= control how much disk space the journal may use up at most. SystemKeepFree= and RuntimeKeepFree= control how much disk space systemd-journald shall leave free for other uses. systemd-journald will respect both limits and use the smaller of the two values.
  The first pair defaults to 10% and the second to 15% of the size of the respective file system, but each value is capped to 4G.
  
  If anything I tend to have the opposite problem: whoops I forgot to set up logrotate for this log file I set up 6 months ago and now my disk is completely full. Never happens for stuff that goes to journald.
  
  It can be, but the defaults are freaking stupid and often do not work.
  
  Aren’t the defaults set by your distro?
  
  AAfaict Debian uses the upstream defaults.
- Still boggles my mind that systemd being terrible is still a debate. Like of all things, wouldn’t text logs make sense?
  
  Wait… it doesn’t store them in plaintext?
  
  Nope, you need journalctl to read.
  
  That’s asinine.
  
  Yeah, and you need systemd to read the binary logs. Though I think there may be a setting to change to text logs, I am not sure because I avoid systemd when I can
  
  Wouldn't compressed logs make even more sense (they way they're now)?

62 comments