• wildbus8979
    link
    fedilink
    arrow-up
    28
    arrow-down
    3
    ·
    edit-2
    4 months ago

    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.

    • Regalia@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      26
      arrow-down
      1
      ·
      edit-2
      4 months ago

      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.

      • Max-P@lemmy.max-p.me
        link
        fedilink
        arrow-up
        13
        ·
        4 months ago

        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.

      • wildbus8979
        link
        fedilink
        arrow-up
        6
        arrow-down
        2
        ·
        edit-2
        4 months ago

        It can be, but the defaults are freaking stupid and often do not work.

    • tentacles9999@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 months ago

      Still boggles my mind that systemd being terrible is still a debate. Like of all things, wouldn’t text logs make sense?