| 1 |
On Mon, Sep 22, 2014 at 8:41 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> On this machine (the one I'm using now) journald is writing its |
| 3 |
> files to /run/log/journal/ instead of /var/log/journal/ |
| 4 |
|
| 5 |
Check the config: |
| 6 |
/etc/systemd/journald.conf: |
| 7 |
|
| 8 |
Storage= |
| 9 |
Controls where to store journal data. One of "volatile", |
| 10 |
"persistent", "auto" and "none". If |
| 11 |
"volatile", journal log data will be stored only in memory, |
| 12 |
i.e. below the /run/log/journal hierarchy |
| 13 |
(which is created if needed). If "persistent", data will be |
| 14 |
stored preferably on disk, i.e. below the |
| 15 |
/var/log/journal hierarchy (which is created if needed), |
| 16 |
with a fallback to /run/log/journal (which is |
| 17 |
created if needed), during early boot and if the disk is |
| 18 |
not writable. "auto" is similar to |
| 19 |
"persistent" but the directory /var/log/journal is not |
| 20 |
created if needed, so that its existence |
| 21 |
controls where log data goes. "none" turns off all |
| 22 |
storage, all log data received will be dropped. |
| 23 |
Forwarding to other targets, such as the console, the |
| 24 |
kernel log buffer or a syslog daemon will still |
| 25 |
work however. Defaults to "auto". |
| 26 |
|
| 27 |
As others frequently point out not everybody likes the journal so you |
| 28 |
can use syslog and just keep the journal in /run where it will not be |
| 29 |
persistent. If that isn't the desire, make sure the config isn't set |
| 30 |
to volatile. |
| 31 |
|
| 32 |
-- |
| 33 |
Rich |
Archives