frodovdr
/
log2ram
mirror of https://github.com/azlux/log2ram.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

typo

This commit is contained in:
azlux 2016-10-17 10:12:32 +02:00 committed by GitHub
parent 9a87d0f940
commit c8c0e1a392
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -19,7 +19,7 @@ into /usr/local/bin/log2ram
## Customize
#### services :
If you open the file `/etc/systemd/system/log2ram.service` , you will see a line starting with `Before=`, you can list here the services who need to start after log2ram, it's append when services start too fast and stop running because log2ram mount a ram folder in the same place.
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.
For example, If you use apache instead of nginx, add `apache2.service` into this line.
@ -28,7 +28,7 @@ Into the file `log2ram` (or `/usr/local/bin/log2ram` if you have already install
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"
The second variable can be set to `true` if you prefer "rsync" than "cp".
###It is working ?
You can now check the mount folder in ram with