The one that springs to mind is the Mosquitto won't start on boot after raspbian and emonsd update thread, but this topic has come up many times so there will be no doubt be several more.
I’ve tried log2ram and found it works really well, I have since modified a fork to improve things further by relocating the rotated files destination to disc rather than holding them in RAM.
Simply maintaining an on disk copy of the tmp log files/folders resolves many of the issues we face without overly complicating things.
- All the files and folders are present at start up with the right structure,ownership and permission levels without maintaining any lists.
- All logfiles are persisted across reboots as they are persisted at shutdown as well as hourly.
- Works transparently with installing new software as any newly installed log files/folders will get copied within the hour or it can be triggered manually (although unnecessary if rebooting)
Plus
- All the rotated files held on disc rather than in RAM reduces the RAM usage, minimizing any chance of the FS choking and a much longer history can be retained too, no longer would we need to debug within a couple of hours (without rebooting) in hope of finding some usable log entries before they are rotated out or lost in a reboot. The /var/log folder is much tidier too without the rotated logs cluttering the place up.
If there is any interest in reviewing or discussing this option too, We can start another thread.