[OE-core] [PATCH] systemd: Instruct the journal to always be volatile

[Khem Raj]

On Wed, Mar 11, 2015 at 9:18 PM,  <randy.e.witt at linux.intel.com> wrote:
>>
>>> On Mar 11, 2015, at 2:28 PM, Randy Witt <randy.e.witt at 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.
> The distro could still change it with a bbappend or additional
> configuration files just like other settings. We don't have an option for
> a persistent journal so I'm curious, how would both cases work currently?
>

No they dont and I have posted a patch which potentially should.

> Currently if a persistent journal is desired, the /var/log symlink has to
> be changed to point to persistent storage, or /var/volatile has to be
> dropped from /etc/fstab. These are also configuration changes.
>
> The lesser of the two evils seems to be making it so that the journal
> works in the volatile case, which is all we've ever supported in poky. If
> a user wanted a non-volatile journal it was left to them to do.

poky is not only the distro thats fed with OE-Core there are several
open ones and several
which are maintained by companies

>
> I agree that the journal should be persistent, but I also agree with
> Richard that seems to be too big of a change in behavior when we're so
> close to the release point.

what makes you think the change you posted is not intrusive, we have a
regression compared to last release,
this patch does not fix the regression, it infact pacifies some errors
which are new and creates yet another behavior.  think of people who
will be migrating from 1.7 to 1.8  problems should be solved in best
possible way.
I am fine with whatever is accepted solution. I have no interest in
push one or the other
I do have a solution which fixes my problems therefore I am less
concerned. Carrying a couple of local reverts it not a big of a deal.

-Khem