From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemd: Instruct the journal to always be volatile
Date: Thu, 12 Mar 2015 08:04:11 +0000 [thread overview]
Message-ID: <1426147451.9114.82.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKqBs7sqNMrTESE_fiNfnRO3jLYTDoUkE4twwgczSU=L2g@mail.gmail.com>
On Thu, 2015-03-12 at 04:18 -0300, Otavio Salvador wrote:
> On Thu, Mar 12, 2015 at 12:09 AM, Khem Raj <raj.khem@gmail.com> wrote:
> >
> >> On Mar 11, 2015, at 2:28 PM, Randy Witt <randy.e.witt@linux.intel.com> wrote:
> >>
> >> When the storage mode for the journal is "auto" if /var/log/journal
> >> exists then the journal will flush to /var/log/journal assuming that
> >> /var/log/journal is persistent.
> >>
> >> However /var/log -> /var/volatile/log in poky, so even though
> >> /var/log/journal exists, it is still volatile.
> >>
> >> Since this can cause ordering issues due to /var/volatile needing to be mounted before the journal actually writes to it, just specify that the journal
> >> should always be volatile and never try to write to "persistent"
> >> storage. The journal will exist in /run/log/journal only.
> >>
> >> This also disables the "After" of the journal on var-volatile.mount
> >> since the ordering is no longer necessary when the journal is only
> >> stored in /run/log/journal.
> >>
> >> [Yocto #7388]
> >
> >
> > This is not right. What if I want persistent logs.? the options is just gone. Both cases should work. /var/volatile should only be used
> > when doing ro-rfs its not FHS specified anyway. Lets not go with this patch.
>
> Agreed.
This isn't quite so simple as "agreed". Are we saying that we want to
rework volatiles handling after feature freeze?
My view on this is that yes, we do need to do something about it, but
right now during stabilisation is not the right time. Particularly when
the patches proposed aren't even tested with sysvinit.
So I'm interested in patches which make things work better without
making fundamental changes now. We can look at changing volatiles with a
properly thought out plan in the next development cycle.
Making the systemd configuration match the rest of the default system
setup would seem to be sensible. We should make it possible for others
to override that if their setup isn't volatile.
Cheers,
Richard
next prev parent reply other threads:[~2015-03-12 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 21:28 [PATCH] systemd: Instruct the journal to always be volatile Randy Witt
2015-03-12 3:09 ` Khem Raj
2015-03-12 4:18 ` randy.e.witt
2015-03-12 4:56 ` Khem Raj
2015-03-12 7:18 ` Otavio Salvador
2015-03-12 8:04 ` Richard Purdie [this message]
2015-03-12 8:13 ` Otavio Salvador
2015-03-12 8:40 ` Khem Raj
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=1426147451.9114.82.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.