|
@@ -19,6 +19,13 @@ into /usr/local/bin/log2ram |
|
|
- You can change the SIZE variable if necessary |
|
|
- You can change the SIZE variable if necessary |
|
|
- If you prefer to use rsync, you can set the USE_RSYNC variable to `true` |
|
|
- If you prefer to use rsync, you can set the USE_RSYNC variable to `true` |
|
|
|
|
|
|
|
|
|
|
|
**###############** |
|
|
|
|
|
|
|
|
|
|
|
**If you install other services who need a /var/log folder (like mysql, apache, nginx) don't forget to run `sudo /usr/local/bin/log2ram write |
|
|
|
|
|
` to be sure the folder will exist if you reboot before one hour after the log2ram install. The best way is to install log2ram after all other** |
|
|
|
|
|
|
|
|
|
|
|
**##############** |
|
|
|
|
|
|
|
|
## Customize |
|
|
## Customize |
|
|
#### services : |
|
|
#### services : |
|
|
If you open the file `/etc/systemd/system/log2ram.service` , you will see a line starting by `Before=`, you can list here the services who need to start after log2ram. You will need to change this line when a service start too fast and stop running because log2ram mount a ram folder where it has start to write log. |
|
|
If you open the file `/etc/systemd/system/log2ram.service` , you will see a line starting by `Before=`, you can list here the services who need to start after log2ram. You will need to change this line when a service start too fast and stop running because log2ram mount a ram folder where it has start to write log. |
|
|