log2ram/README.md

71 lines
2.9 KiB
Markdown
Raw Normal View History

2016-04-18 12:02:10 +02:00
# Log2Ram
2016-10-20 12:47:56 +02:00
Like ramlog for systemd (on debian 8 jessie for example).
2016-04-20 10:47:39 +02:00
Usefull for **RaspberryPi** for not writing on the SD card all the time. You need it because your SD card doesn't want to suffer anymore!
2016-04-18 12:03:41 +02:00
Explanations: The script creates a `/var/log` mount point in RAM. So any writing of the log to the `/var/log` folder will not actually be written to disk (in this case to the sd card for a raspberry card) but directly to RAM. By default, every hour, the CRON will launch a synchronization of the RAM to the folder located on the physical disk. The script will also make this copy of RAM to disk in case of machine shutdown (but cannot do it in case of power failure). This way you avoid excessive writing on the SD card.
2017-04-27 11:24:05 +02:00
The script [log2ram](https://github.com/azlux/log2ram) can work on every linux system. So you can use it with your own daemon manager if you don't have systemd.
2016-10-20 12:47:56 +02:00
2016-04-18 12:02:10 +02:00
Log2Ram is based on transient log for Systemd here : [A transient /var/log](https://www.debian-administration.org/article/661/A_transient_/var/log)
2018-04-23 18:11:06 +02:00
_____
## Menu
1. [Install](#install)
2. [Upgrade](#upgrade)
3. [Customize](#customize)
4. [It is working ?](#it-is-working)
5. [Uninstall](#uninstall-)
2016-04-18 12:03:41 +02:00
## Install
curl -Lo log2ram.tar.gz https://github.com/azlux/log2ram/archive/master.tar.gz
tar xf log2ram.tar.gz
2018-01-15 08:57:14 +01:00
cd log2ram-master
2018-03-03 19:45:34 +01:00
chmod +x install.sh && sudo ./install.sh
2018-02-18 20:40:38 +01:00
cd ..
rm -r log2ram-master
**REBOOT** before installing anything else (for example apache2)
2018-04-23 18:11:06 +02:00
## Upgrade
You need to stop log2ram (`service log2ram stop`) and start the [install](#install).
2017-04-11 18:57:52 +02:00
2016-10-11 15:18:54 +02:00
## Customize
#### variables :
In the file `/etc/log2ram.conf`, there are three variables:
2016-10-11 15:18:54 +02:00
- `SIZE`: defines the size the log folder will reserve into the RAM (default is 40M).
- `USE_RSYNC`: Can be set to `true` if you prefer ´rsync´ rather than ´cp´. I use the command `cp -u` and `rsync -X`, I don't copy the all folder every time for optimization.
- `MAIL`: Disables the error system mail if there is not enough place on RAM (if set to `false`)
2017-04-27 11:24:05 +02:00
#### refresh time:
By default Log2Ram writes to the HardDisk every hour. If you think this is too much, you can make the write every day by moving the cron file to daily: `sudo mv /etc/cron.hourly/log2ram /etc/cron.daily/log2ram`.
2016-10-11 15:18:54 +02:00
### It is working?
2017-04-27 11:24:05 +02:00
You can now check the mount folder in ram with (You will see lines with log2ram if working)
2016-04-18 12:09:32 +02:00
```
# df -h
log2ram 40M 532K 40M 2% /var/log
# mount
log2ram on /var/log type tmpfs (rw,nosuid,nodev,noexec,relatime,size=40960k,mode=755)
2016-04-18 12:09:32 +02:00
```
2017-04-27 11:24:05 +02:00
If you have issue with apache2, you can try to add `apache2.service` next to other services on the `Before` parameter in `/etc/systemd/system/log2ram.service` it will solve the pb
2017-12-28 17:41:49 +01:00
The log for log2ram will be written at: `/var/log/log2ram.log`
2016-04-20 10:47:39 +02:00
###### Now, muffins for everyone!
2017-07-27 20:13:51 +02:00
## Uninstall :(
(Because sometime we need it)
```
chmod +x /usr/local/bin/uninstall-log2ram.sh && sudo /usr/local/bin/uninstall-log2ram.sh
2017-10-02 00:50:31 +02:00
```