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.
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.
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
Holy shit
right? what the hell?
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.
If you don’t use archaic technologies it actually does.
systemd-journaldis limited to max(10% FS size, 4GB) per default.Well, Linux is also made for servers and super computers, and just imagine it refusing to keep logs because the file’s too large
Well it’s better than a server locking up from a full disk.
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.
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.