You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customize variables :
In the file /etc/log2ram.conf, there are five variables:
SIZE: defines the size the log folder will reserve into the RAM (default is 40M).
USE_RSYNC: (commented out by default = true) use cp instead of rsync (if set to false).
However the RSYNC option seems to have been modified to simply be used if rsync is present (which I appreciate).
That chunk should be removed from the README.md?
That would leave 4 customization options, but there are 6 present now. The missing 2 from the README.md file:
COMP_ALG=lz4
LOG_DISK_SIZE=100M
Ripe for addition.
On the subject of LOG_DISK_SIZE=100M I have a question (which was why I noticed the README was looking long in the tooth).
Do I need to update LOG_DISK_SIZE=100M if I up SIZE=? For example I'm running SIZE=400M (I've got additional folders I'm managing using PATH_DISK and have lots of extra RAM for my needs).
The text was updated successfully, but these errors were encountered:
As far as I understand it, LOG_DISK_SIZE= should be what the uncompressed (max) size of all dirs you have in the PATH_DISK= would need to be. The 'potentially used RAM if ZL2R is set to true' is what SIZE= needs to be. So, for example, in my use-case;
I do not use compression, because I use log2ram mostly for speed improvement (using a ramdisk), rather than preventing diskwrites/access.
ZL2R is set to default (false), COMP_ALG then does/means nothing.
I have set both SIZE= and LOG_DISK_SIZE= to the same value. In my case, 8192M.
Minor documentation item:
README.md mentions:
However the RSYNC option seems to have been modified to simply be used if rsync is present (which I appreciate).
Ripe for addition.
On the subject of LOG_DISK_SIZE=100M I have a question (which was why I noticed the README was looking long in the tooth).
Do I need to update LOG_DISK_SIZE=100M if I up SIZE=? For example I'm running SIZE=400M (I've got additional folders I'm managing using PATH_DISK and have lots of extra RAM for my needs).
The text was updated successfully, but these errors were encountered: