Isaac

Alright, I got it, thank you! I commented out all the lines in the syncToDisk function (in log2ram code) and replaced them with one "echo "Ok"" (since it was giving me some strange error when I left it all blank). It works like magic! I now modified the log2ram code to give the user an option in the configuration file to do this (i.e. to never write the logs back to the disk). We'll see if he accepts my pull request. Regarding the other issue, logrotate could rotate the logs in the /var/log tmpfs partition in RAM, so that if the computer is running for many days straight, the 40 MB partition shouldn't fill (note: under my arrangement, when the computer reboots /var/log empties anyway - with the exception of the boot log). If it does fill, I could always set logrotate to run more frequently or save fewer logs. Thanks again! Isaac

I see. He says to insert a clause into those lines to exclude certain files. Are you hinting that if I take out those rsync lines all together it will never sync to the disk at all (but otherwise function properly)? Also, regarding RAM filling up, deleting the logs between sessions would normally do the trick, but I'm trying to prevent a situation where I'd keep a computer logged in for a long time or do something that results in lots of messages being written to the logs and the RAM disk would fill up.

Hi, I'd like to setup log2ram so that it never writes to the disk, but rather discards all logs at shutdown. The documentation for log2ram says that if I delete /etc/cron.daily/log2ram it will only sync the logs to the disk at shutdown. But is there a way to have it not even do that? Also, in order to prevent log2ram from filling up all its space in RAM, is it possible to setup an overwrite mechanism so that the logs begin overwriting themselves once they hit the space limit?