this post was submitted on 19 Aug 2025
586 points (99.0% liked)

linuxmemes

26960 readers
1024 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    Well, not a noob, more like an idiot πŸ˜‚ EDIT: Yes, on the same drive as my Home folder, etc. And yes, technically they're snapshots, not backups.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] xilophor@lemmy.world 72 points 1 week ago* (last edited 1 week ago) (3 children)

    500 GiB syslog

    I've been in a similar situation

    edit: For context, there was a bug with the graphics driver that was putting out an error every frame, at 200+ fps... needless to say, I could actively see the log growing in size

    [–] JustAnotherKay@lemmy.world 25 points 1 week ago (1 children)
    [–] alecsargent@lemmy.zip 11 points 1 week ago

    right? what the hell?

    [–] MangoPenguin@lemmy.blahaj.zone 8 points 1 week ago (2 children)

    This is what confuses me about Linux defaults, why would it let them grow that large?

    We can tune logging settings to resonable values for the max size and everything, it just doesn't come that way for some reason.

    [–] faerbit@sh.itjust.works 18 points 1 week ago

    If you don't use archaic technologies it actually does. systemd-journald is limited to max(10% FS size, 4GB) per default.

    [–] Chrobin@discuss.tchncs.de 13 points 1 week ago (1 children)

    Well, Linux is also made for servers and super computers, and just imagine it refusing to keep logs because the file's too large

    [–] MangoPenguin@lemmy.blahaj.zone 8 points 1 week ago (1 children)

    Well it's better than a server locking up from a full disk.

    [–] Chrobin@discuss.tchncs.de 7 points 1 week ago (1 children)

    But I think it's better for it to fail from expected behavior vs unexpected behavior. Your storage being full is very transparent and expected, but that a file reaches max size and starts cutting off is unexpected and would surprise a lot of people.

    I myself use supercomputers and the log files can get into a lot of GB, and I would hate it if it just cut off at some point.

    I mean that's fair, but a supercomputer would be heavily customized so disabling log limits would be part of that if needed.

    [–] rumba@lemmy.zip 5 points 1 week ago

    Mmmm somebody need some log rotate in their life.

    Oh my production s***'s on point but all the Dave and QA s*** I need at least one failure before I get around to doing law rotate. I guess I should spend the time to make the ansible job.