Azlux

infinity : Yes it's will work. It's do the same as hardvk0 script. 

when are they written do SD card finally?
-> It's a systemd script, so the log are written when the service stop
 
What triggers the writing to SD-Card
-> On a halt, a restart of the service or of the computer
 
is your script meant to be always holding the logs in Ramdisk, thus losing all logs after a reboot
-> No. You will lose your log only if your machine stop brutally (electricity failure for example)
 
what happens if your "SIZE=25M" is full with logs
-> it's like a partition for the log software (syslog) , the syslog will stop writting if it's full until your log rotate with logrotate.It's why you need to adapt this value. you can check the size with : df -h
 
Does Log2Ram delete then the oldest logs according to a rotating principle?
-> It's the job of logrotate, the job of log2ram is to mount a ram folder for your /var/log folder.
 
 

Hi,
1. The mount folder is a tmpfs, it a static size. So the SIZE variable define the maximal size you allocate into your RAM for the log folder. (Mine is around 25MB)
2. You can make a CRON to make a 'service log2ram restart'. Into my script, the restart function copy the content into the initial disk folder

Thank for your suggestions.
You can modify the code depending of your needs. (On a raspberry, 256Mb is the half of my RAM)
The option -u of the cp make a update
-u, --update copy only when the SOURCE file is newer than the destination file or when the destination file is missing I think it's enough.
But I will add yours improvements like a option. (Because I like minimalist program without dependencies)

/etc/cron.daily/log2ram:
#!/bin/sh test -x /usr/local/bin/log2ram || exit 0 /usr/local/bin/log2ram write

Yes it should. If not, do not hesitate to open an issue on github
I use basic functions of debian jessie, I don't see any problem for log2ram for working on your system.