Jump to content

barish

Members
  • Posts

    76
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Bremen Germany

Contact Methods

  • Website URL
    https://nashorn.eu
  • Github
    heaterC

Recent Profile Visitors

2762 profile views
  1. Due to systemd, Journal is going to replace all journals sooner or later, it's already one of the busiest journaling on the sytem. The logs are binary and can't be rotated like text logs, they are already compressed and can't be read by text editor, instead only by journalctl. Thus, in /usr/lib/armbian/armbian-ramlog , the directory /var/log/journal is excluded from standard log rotation and copying to HDD. Instead, it is copied once to /var/log.hdd/journal and a soft-link is created: /var/log/journal pointing to -> /var/log.hdd/journal . The RAM logging was introduced to spare the SD card, preventing many write actions that wear the SD card quickly. But this really busy log, including all system messages, is now written directly to the SD card. If this is the only way of preserving older systemd logs, shouldn't we then at least reconfigure journald in a way to e.g. log into RAM /run/log/journal and only snyc to SD card every n hours? Or maybe we could reduce the log level of journald (which is by default "debug") to e.g. "err" and reduce the write activity in that way? For me, it appears right now, that all the benefits of logging to RAM disk are canceled out by having journald log to SD card? Please correct me if I am mistaken in any of my assumptions above.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines