Here are the important lines of /etc/systemd/journald.conf
[Journal] Storage=volatile RuntimeMaxUse=32M RuntimeMaxFileSize=8M RuntimeMaxFiles=4 ForwardToConsole=no ForwardToWall=noThat will log to RAM only, a maximum of 32M in up to 4 files, so it should automatically prune 25% when it gets full, but I'm often having to do it manually with:-
journalctl --vacuum-files 3
It's the config that needs to be optimised.
---druck
+1. And this actually works
I haven't done mine manually. Ever.
Well that was where a ramdisk is handy to replace /var/log
There is a command that looks at real I/O calls to e.g. disk drives. It should return zero ponce you achieve Nirvana...
Exactly why I wish systemd would FOAD!
---druck
Trust me, it can be done systenmd does NOT carry on logging. My system is up months at a time and I never need to manually shrink it
Everything else is a matter of picking through anything that logss an either diverting it to a RAM disk at configuration level, or symlinking is entry in /var/log to a ramdisk It takes time and the thing you may well lack, patience.
Ironically, it’s the one thing you can configure to work exactly the way you want.
As long as its the systemd way :-)
Actually linux has always been very configurable the way you want, probably too configurable, because the plethora of options/alternatives etc can put people off.
Chris Green snipped-for-privacy@isbd.net schrieb:
Since I began using industrial grade cards (e.g. Kingston industrial) I never had any issues with a defective card any more. Those cards may not be the fastest, but they have proven to be very reliable.
The “systemd way” lets you send the logging wherever you want. Want it all to go to rsyslog? Send it there. Then you can blame rsyslog for eating your SD-card, not systemd.
Oh dear you took it waaayyy too seriously! I never said it couldn't! I merely meant that, in the bits you edited out, that you could even Before Systemd "configure [it] to work exactly the way you want". But obviously I touched one of your buttons, as you did mine :-)
And to be more on topic, I'd suggest to the original poster, that having a local syslog log server is useful. Configure your RPi machine to send the log entries to that. No SD writes and the logs are there even if the SD card gets corrupt for other reasons.
As I recall, the original complaint was about logfiles shortening the life of SD cards. How would this have helped?
Have something to add? Share your thoughts — no account required.
Ask the community — no account required