You could look at Rsyslog and add your own filters.
Log2Ram etc can help you manage them.
Spend a bit of time examining the log first and see if there are any processes putting out debug messages that can be turned off (Python programs using Adafruit libraries where a major cause here as I left my debugging on![:oops:]( "Embarrassed")
) and if there are any system processes that you could filter status messages from (IIRC the random number generator drops lots of info and can be replaced with a 'quieter' one).
The only way you can keep the info over reboot is to write it to disk - this comes with the risk of corruption if power drops - even if you use a USB mounted device than that could get corrupt BUT you should still have a working system that can correct the software based disk errors.
Best solution though is to invest in a UPS and handle power cuts correctly !!!
Log2Ram etc can help you manage them.
Spend a bit of time examining the log first and see if there are any processes putting out debug messages that can be turned off (Python programs using Adafruit libraries where a major cause here as I left my debugging on
) and if there are any system processes that you could filter status messages from (IIRC the random number generator drops lots of info and can be replaced with a 'quieter' one).The only way you can keep the info over reboot is to write it to disk - this comes with the risk of corruption if power drops - even if you use a USB mounted device than that could get corrupt BUT you should still have a working system that can correct the software based disk errors.
Best solution though is to invest in a UPS and handle power cuts correctly !!!
Statistics: Posted by MiscBits — Sun Jun 23, 2024 2:20 pm