public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] journald refuses to put log files in /var/log/journal/
Date: Mon, 22 Sep 2014 20:52:05 -0400	[thread overview]
Message-ID: <CAGfcS_=xoUud+6DxPvVOJZmr-1q71X6M5O7DzW7hb2_5rxgiBw@mail.gmail.com> (raw)
In-Reply-To: <lvqfk1$157$1@ger.gmane.org>

On Mon, Sep 22, 2014 at 8:41 PM, walt <w41ter@gmail.com> 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


  reply	other threads:[~2014-09-23  0:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  0:41 [gentoo-user] journald refuses to put log files in /var/log/journal/ walt
2014-09-23  0:52 ` Rich Freeman [this message]
2014-09-23  3:50 ` Canek Peláez Valdés
2014-09-23 14:27   ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [SOLVED] walt
2014-09-23 14:46     ` Rich Freeman
2014-09-23 17:40       ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [NOT SOLVED] walt
2014-09-23 18:28         ` Mike Gilbert
2014-09-23 18:42           ` Rich Freeman
2014-09-23 21:55           ` [gentoo-user] Re: journald refuses to put log files in /var/log/journal/ [REALLY SOLVED] walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_=xoUud+6DxPvVOJZmr-1q71X6M5O7DzW7hb2_5rxgiBw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox