ramlog like for systemd (Put log into a ram folder)
Go to file
azlux 9f60f97849
fix readme, add fecture
Added:
- check on install
- clear old folder on install
- better uninstall script
- use systemctl instead of manually call script in the cron
2017-12-16 12:15:39 +01:00
LICENSE Update 2017-04-12 13:28:56 +02:00
README.md Fixed consistent naming of /var/hdd.log 2017-12-07 17:42:40 +01:00
install.sh Bug fix: avoid installing when still installed 2017-12-16 11:42:37 +01:00
log2ram Revert "Added start, write and stop logging" 2017-12-10 22:37:51 +01:00
log2ram.conf mail if error 2017-07-18 00:46:54 +02:00
log2ram.hourly Fixed: use systemctl reload to write changes to disk and to the log 2017-12-10 22:53:48 +01:00
log2ram.service Update log2ram.service 2017-10-09 13:33:20 +02:00
uninstall.sh Fixed consistent naming of /var/hdd.log 2017-12-07 17:42:40 +01:00

README.md

Log2Ram

Like ramlog for systemd (on debian 8 jessie for example).

Usefull for Raspberry for not writing all the time on the SD card. You need it because your SD card don't want to suffer anymore !

The script log2ram can work on every linux system. So you can use it with your own daemon manager if you don't have systemd.

Log2Ram is based on transient log for Systemd here : A transient /var/log

Install

git clone https://github.com/azlux/log2ram.git
cd log2ram
chmod +x install.sh
sudo ./install.sh

REBOOT before installing anything else (for example apache2)

Customize

variables :

Into the file /etc/log2ram.conf, there are three variables :

  • The first variable define the size the log folder will reserve into the RAM.
  • The second variable can be set to true if you prefer "rsync" than "cp". I use the command cp -u and rsync -X, I don't copy the all folder every time for optimization.
  • The last varibale disable the error system mail if there are no enought place on RAM (if set on false)

refresh time:

The default is to write log into the HardDisk every hour. If you think this is too much, you can make the write every day by moving the cron file : sudo mv /etc/cron.hourly/log2ram /etc/cron.daily/log2ram.

It is working ?

You can now check the mount folder in ram with (You will see lines with log2ram if working)

df -h
mount

If you have issue with apache2 , you can try to add apache2.service next to other services on the Before parameter into /etc/systemd/system/log2ram.service it will solve the pb

The log for log2ram will be write here : /var/hdd.log/log2ram.log

Now, muffins for everyone !

Uninstall :(

(Because sometime we need it)

cd log2ram
chmod +x uninstall.sh
sudo ./uninstall.sh