heuzef
/
log2ram
mirror of https://github.com/azlux/log2ram.git
1
0
Fork 0
Code Issues 0 Releases 18 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
177 Commits
3 Branches
616 KiB
 
Tree: 1a61e1eea5
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '1a61e1eea5'
${ noResults }
log2ram/log2ram.conf

45 lines
2.6 KiB
Raw Blame History 

  1. # Configuration file for Log2Ram (https://github.com/azlux/log2ram) under MIT license.

  2. # This configuration file is read by the log2ram service

  3. 

  4. # Size for the ram folder, it defines the size the log folder will reserve into the RAM.

  5. # If it's not enough, log2ram will not be able to use ram. Check you /var/log size folder.

  6. # The default is 40M and is basically enough for a lot of applications.

  7. # You will need to increase it if you have a server and a lot of log for example.

  8. SIZE=128M

  9. 

  10. # Select the log syncing method between the log directory on disk and in the RAM.

  11. # The variable may be uncommented out, setting it to false, if "cp" is preferred over "rsync".

  12. # Currently, this option needs to be unset or set to true for "rsync" to run,

  13. # with "cp" available for fallback when "rsync" is missing.

  14. # In all other cases, setting USE_RSYNC to anything other than true will default to "cp".

  15. #USE_RSYNC=false

  16. 

  17. # If there are some errors with available RAM space, a system mail will be send

  18. # Change it to false and you will have only a log if there is no place on RAM anymore.

  19. MAIL=true

  20. 

  21. # Variable for folders to put in RAM. You need to specify the real folder `/path/folder` , the `/path/hdd.folder` will

  22. # be automatically created. Multiple path can be separeted by `;`. Do not add the final `/` !

  23. # example : PATH_DISK="/var/log;/home/test/FolderInRam"

  24. PATH_DISK="/var/log"

  25. 

  26. # Should log2ram consider journald and do a log rotate before copying the log files back? Please note that for this

  27. # rsync is mandatory. Also make sure that you have configured SystemMaxUse in journald.conf, because the size of this

  28. # ram folder is will probably not be as large as journald will use by default

  29. JOURNALD_AWARE=true

  30. 

  31. # **************** Zram backing conf  *************************************************

  32. 

  33. # ZL2R Zram Log 2 Ram enables a zram drive when ZL2R=true ZL2R=false is mem only tmpfs

  34. ZL2R=false

  35. # COMP_ALG this is any compression algorithm listed in /proc/crypto

  36. # lz4 is fastest with lightest load but deflate (zlib) and Zstandard (zstd) give far better compression ratios

  37. # lzo is very close to lz4 and may with some binaries have better optimisation

  38. # COMP_ALG=lz4 for speed or Zstd for compression, lzo or zlib if optimisation or availabilty is a problem

  39. COMP_ALG=lz4

  40. # LOG_DISK_SIZE is the uncompressed disk size. Note zram uses about 0.1% of the size of the disk when not in use

  41. # LOG_DISK_SIZE is expected compression ratio of alg chosen multiplied by log SIZE

  42. # lzo/lz4=2.1:1 compression ratio zlib=2.7:1 zstandard=2.9:1

  43. # Really a guestimate of a bit bigger than compression ratio whilst minimising 0.1% mem usage of disk size

  44. LOG_DISK_SIZE=256M