1
0
mirror of https://github.com/azlux/log2ram synced 2024-11-23 22:06:10 +00:00

Compare commits

..

No commits in common. "2e8d06b807e921fa5609db46637f9d54d75b723e" and "bf8f16bba6ce5a697e74af0a22a8974b08620ac7" have entirely different histories.

2 changed files with 0 additions and 7 deletions

View File

@ -129,12 +129,6 @@ If the `/var/log/journal` is very large, then there are a lot of system logs. De
SystemMaxUse=20M SystemMaxUse=20M
``` ```
**Or** the more radical version of directly flushing the journal to a size that matches log2ram size imediately _(Be aware that this flish flush the systemd journal logs imediately to the given size!)_
```bash
journalctl --vacuum-size=32M
```
This should be set to a value smaller than the size of the RAM volume; for example, half of it could be fine. Then, apply the new setting: This should be set to a value smaller than the size of the RAM volume; for example, half of it could be fine. Then, apply the new setting:
```bash ```bash

View File

@ -63,7 +63,6 @@ sync_from_disk() {
if [ -n "$(du -sh -t "$TP_SIZE" "$HDD_LOG"/ | cut -f1)" ]; then if [ -n "$(du -sh -t "$TP_SIZE" "$HDD_LOG"/ | cut -f1)" ]; then
echo "ERROR: RAM disk for \"$HDD_LOG/\" too small. Can't sync." echo "ERROR: RAM disk for \"$HDD_LOG/\" too small. Can't sync."
echo -e "File(s) causing issues\n: $(du -sh -t "$TP_SIZE" "$HDD_LOG"/*)"
umount -l "$RAM_LOG"/ umount -l "$RAM_LOG"/
umount -l "$HDD_LOG"/ umount -l "$HDD_LOG"/
if [ "$MAIL" = true ]; then if [ "$MAIL" = true ]; then