this post was submitted on 01 Aug 2024
663 points (98.5% liked)

linuxmemes

21263 readers
1114 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] wildbus8979@sh.itjust.works 25 points 3 months ago* (last edited 3 months ago) (2 children)

    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 25 points 3 months ago* (last edited 3 months ago) (2 children)

    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 13 points 3 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@sh.itjust.works 4 points 3 months ago* (last edited 3 months ago) (1 children)

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

    [–] Starbuck@lemmy.world 18 points 3 months ago (1 children)

    Aren’t the defaults set by your distro?

    [–] wildbus8979@sh.itjust.works 2 points 3 months ago

    AAfaict Debian uses the upstream defaults.

    [–] tentacles9999@lemmynsfw.com 5 points 3 months ago (2 children)

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

    [–] acockworkorange@mander.xyz 5 points 3 months ago (2 children)

    Wait… it doesn’t store them in plaintext?

    [–] uranibaba@lemmy.world 4 points 3 months ago (1 children)

    Nope, you need journalctl to read.

    [–] acockworkorange@mander.xyz 2 points 3 months ago

    That’s asinine.

    [–] tentacles9999@lemmynsfw.com 3 points 3 months ago

    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

    [–] fallingcats@discuss.tchncs.de 4 points 3 months ago

    Wouldn't compressed logs make even more sense (they way they're now)?