On Mon, Sep 22, 2014 at 8:41 PM, walt <[email protected]> wrote:
> On this machine (the one I'm using now) journald is writing its
> files to /run/log/journal/ instead of /var/log/journal/
Check the config:
/etc/systemd/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 daemon will still
work however. Defaults to "auto".
As others frequently point out not everybody likes the journal so you
can use syslog and just keep the journal in /run where it will not be
persistent. If that isn't the desire, make sure the config isn't set
to volatile.
--
Rich
