packet:bpq_logging_reduction
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
packet:bpq_logging_reduction [2025/04/13 06:43] – [Writing all linbpq packets to syslog] m0mzf | packet:bpq_logging_reduction [2025/04/14 20:05] (current) – [Newer versions of Raspberry Pi OS (i.e. Debian 12)] m0mzf | ||
---|---|---|---|
Line 73: | Line 73: | ||
< | < | ||
- | There will still be some stuff ending up in /var/log - on a Debian system this will be logs from apt, dpkg etc, but all syslogging will now be in RAM and sizes kept under control. As the syslog is in RAM rebooting the Pi / if the Pi crashes all the logs will be lost. If you want persistent log storage (for example on a Pi 5 with an NVMe SSD) then you can get some control by vacuuming / configuring journald - that's beyond the scope of "save your SD card" so there' | + | There will still be some stuff ending up in /var/log - on a Debian system this will be logs from apt, dpkg etc, and other packages (ginx, mosquitto etc) by default are configured to write directly to it, but all syslogging will now be in RAM and sizes kept under control. As the syslog is in RAM rebooting the Pi / if the Pi crashes all the logs will be lost. If you want persistent log storage (for example on a Pi 5 with an NVMe SSD) then you can get some control by vacuuming / configuring journald - that's beyond the scope of "save your SD card" so there' |
To see what linbpq has been saying run | To see what linbpq has been saying run |
packet/bpq_logging_reduction.txt · Last modified: 2025/04/14 20:05 by m0mzf