Use volatile storage for journal data #1004

If `/var/log/journal` is present, systemd-journald flushes the log to the disk, which we do not want yet, as we still use syslog. Therefore, remove the directory. We probably had manually deleted it on all systems with systemd 237, and didn’t update the bee file accordingly, so that the logs were kept when updating to systemd 239.

From `man journald.conf`: > Storage= > Controls where to store journal data. One of "volatile", > "persistent", "auto" and "none". If "volatile", journal log data > will be stored only in memory, i.e. below the /run/log/journal > hierarchy (which is created if needed). If "persistent", data will > be stored preferably on disk, i.e. below the /var/log/journal > hierarchy (which is created if needed), with a fallback to > /run/log/journal (which is created if needed), during early boot > and if the disk is not writable. "auto" is similar to > "persistent" but the directory /var/log/journal is not created if > needed, so that its existence controls where log data goes. > "none" turns off all storage, all log data received will be > dropped. Forwarding to other targets, such as the console, the > kernel log buffer, or a syslog socket will still work however. > Defaults to "auto".

Use volatile storage for journal data #1004

Use volatile storage for journal data #1004

Commits on Jan 15, 2019