log2ram
log2ram copied to clipboard
ramlog like for systemd (Put log into a ram folder)
While sync_to_disk is executed rsync or cp copies content of path to hdd.path. Logging of this is done at $LOG2RAM_LOG, which is located at $RAM_LOG. In case of executing sync_to_disk...
repeated start) (without stop) does not cause additional "mount --bind" anymore
Tested with systemd 255 on ubuntu 24.04 and 22.04 version 1.7.2 Journal logs are not saved and restored after a system reboot. To test: 1. Clear the journal with journal...
Hello, It seems like my rsync version is not compatible with log2ram. When I run `service log2ram reload` it is supposed to write logs to disk. But instead I get...