For troubleshooting purposes I want to temporarily have logs written immediately to disk rather than to ram. Will this work?

# ramlog OFF
sudo systemctl stop armbian-ramlog
sudo sed -i 's/^ENABLED=.*/ENABLED=false/' /etc/default/armbian-ramlog
sudo systemctl restart rsyslog
sudo journalctl --flush

# ramlog ON
sudo sed -i 's/^ENABLED=.*/ENABLED=true/' /etc/default/armbian-ramlog
sudo systemctl start armbian-ramlog
sudo systemctl restart rsyslog

 

Edited July 27Jul 27 by mc510

good question, never tried this. I usually just set ENABLE to false and reboot.

On 7/27/2026 at 11:07 PM, mc510 said:

For troubleshooting purposes I want to temporarily have logs written immediately to disk rather than to ram. Will this work?

# ramlog OFF
sudo systemctl stop armbian-ramlog
sudo sed -i 's/^ENABLED=.*/ENABLED=false/' /etc/default/armbian-ramlog
sudo systemctl restart rsyslog
sudo journalctl --flush

# ramlog ON
sudo sed -i 's/^ENABLED=.*/ENABLED=true/' /etc/default/armbian-ramlog
sudo systemctl start armbian-ramlog
sudo systemctl restart rsyslog

Temporarily suspending RAM logging should generally be tested carefully, especially if the goal is reducing unnecessary writes or memory usage. Checking the actual logging configuration first can clarify what is consuming resources. For audio-related hardware projects, an Authentic ST TDA7293 amplifier IC may also require proper thermal and power-supply considerations.

Yes, that should work for a temporary troubleshooting test. I’d verify #systemctl status armbian-ramlog# and check #/var/log# afterward to confirm logs are being written directly to disk. Re-enabling ramlog should restore the normal setup.

Edit: For the code, I use # because it was breaking the paragraph when I was using the code option. Sorry

Edited August 6Aug 6 by DavidFajardo