1
0
mirror of https://github.com/azlux/log2ram synced 2024-11-23 13:56:30 +00:00

Compare commits

...

2 Commits

Author SHA1 Message Date
2e8d06b807
Added more output on start failure
Merge pull request #203 from a1466d44-d3dc-4c0b-90c7-315b088731d7/master
2023-02-07 11:02:14 +01:00
97b69f63-601b-4697-90db-7cdf2e2a0ea5
cd96c3c3e8 Added more helpfull output to the huge file failue in the syncFromDisk function, and an example command to flush the systemd journal 2023-01-31 22:56:10 +01:00
2 changed files with 7 additions and 0 deletions

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
```
**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:
```bash

View File

@ -63,6 +63,7 @@ sync_from_disk() {
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 -e "File(s) causing issues\n: $(du -sh -t "$TP_SIZE" "$HDD_LOG"/*)"
umount -l "$RAM_LOG"/
umount -l "$HDD_LOG"/
if [ "$MAIL" = true ]; then