-
systemd-journald writes to /run/log/journal instead of persistent storage with Armbian ramlog
Hi, I am trying to determine whether this is expected behavior or a bug/ordering issue in Armbian's armbian-ramlog. My /etc/systemd/journald.conf contains: Storage=persistent SystemMaxUse=20M Persistent journal storage is available: /var/log/journal -> /var/log.hdd/journal and /var/log.hdd is mounted read-write. However, after every reboot, systemd-journald initially writes to /run/log/journal. I verified this directly: sudo ls -l /proc/$(pidof systemd-journald)/fd | grep journal Immediately after boot I get: 33 -> /run/log/journal/d1d6e2a49fd24499b90cb6d5198cb70e/system.journal So journald is actually holding the runtime journal open. The system has armbian-ramlog enabled. Its unit contains: Before=rsyslog.service sysinit.target syslog.target RequiresMountsFor=/var/log /var/log.hdd Interestingly, running this manually: sudo journalctl --flush immediately switches journald to persistent storage. Afterwards: sudo ls -l /proc/$(pidof systemd-journald)/fd | grep journal shows: 33 -> /var/log.hdd/journal/d1d6e2a49fd24499b90cb6d5198cb70e/system.journal 34 -> /var/log.hdd/journal/d1d6e2a49fd24499b90cb6d5198cb70e/user-1000.journal So the persistent filesystem is definitely accessible and writable. This makes me wonder: Is armbian-ramlog causing systemd-journald to remain on /run/log/journal after boot, or is this simply an ordering issue involving systemd-journal-flush.service? In other words, should armbian-ramlog allow/trigger the journal flush automatically once /var/log.hdd is mounted? Any insight from the Armbian side would be appreciated.
- How to change the LED0 behaviour of RTL8201F PHY
-
How to change the LED0 behaviour of RTL8201F PHY
Hello! Is there a possibility to change the default LED0 behaviour of the RTL8201F PHY? Here is the Datasheet: https://file.elecfans.com/web1/M00/99/0F/o4YBAF0VytaAI7ezABH66fmIRIg854.pdf?filename=RTL8201F-VB-CG.pdf And this is the relevant register: It states, that "11" is the default - but I think it is changed to "00" during driver initialization - is that possible? I would like to change it to "01" - is this somehow possible without recompiling the driver? Thank you! Best regards, Manuel
- Overlays do not apply even when selected in armbian-config and then rebooting
mm2189
Members
-
Joined
-
Last visited