New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README.md out of date regarding Customization #188
Comments
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;
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: