frodovdr/log2ram
1
0
Fork 0
mirror of https://github.com/azlux/log2ram.git synced 2023-10-10 13:37:24 +02:00
Code Issues Projects Releases Wiki Activity

Added more helpfull output to the huge file failue in the syncFromDisk function, and an example command to flush the systemd journal

Browse Source
This commit is contained in:
97b69f63-601b-4697-90db-7cdf2e2a0ea5 2023-01-31 22:56:10 +01:00
parent bf8f16bba6
commit cd96c3c3e8
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -129,6 +129,12 @@ 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

1
log2ram
View File

@ -63,6 +63,7 @@ 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