From: Esben Haabendal <esben@geanix.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: Changqing Li <changqing.li@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] systemd: fix journald persistency when VOLATILE_LOG_DIR is false
Date: Thu, 24 Oct 2024 16:29:10 +0200 [thread overview]
Message-ID: <87seslpoax.fsf@geanix.com> (raw)
In-Reply-To: <58cf7a251cc55641f2d5da7dfedf204e367cc38b.camel@linuxfoundation.org> (Richard Purdie's message of "Thu, 24 Oct 2024 13:58:10 +0100")
"Richard Purdie" <richard.purdie@linuxfoundation.org> writes:
> On Thu, 2024-10-24 at 13:41 +0200, Esben Haabendal via lists.openembedded.org wrote:
>> Commit 18d46e11d85d ("systemd: fix dead link /var/log/README") broke the
>> default systemd behavior when VOLATILE_LOG_DIR is set to false.
>>
>> By not creating the /var/log/journal directory, the default configured
>> systemd (Storage=auto) will silently revert to just doing volatile
>> logging (/run/journal).
>>
>> The problem fixed with the above mentioned commit was specifically related
>> to configurations where VOLATILE_LOG_DIR is true, in which case it should
>> be perfectly fine to not create the /var/log/journal directory, so we
>> should be able to keep the fix in place, while not breaking behavior for
>> non VOLATILE_LOG_DIR configurations.
>>
>> Signed-off-by: Esben Haabendal <esben@geanix.com>
>> ---
>> meta/recipes-core/systemd/systemd_256.6.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_256.6.bb b/meta/recipes-core/systemd/systemd_256.6.bb
>> index 68f15ab065dd5985e4e5cefc2cd005dba5ac9c7f..88ee0c8a7f89726fc9be489f3fc419f9feb37251 100644
>> --- a/meta/recipes-core/systemd/systemd_256.6.bb
>> +++ b/meta/recipes-core/systemd/systemd_256.6.bb
>> @@ -254,7 +254,7 @@ EXTRA_OEMESON += "-Dnobody-user=nobody \
>> -Dsystem-uid-max=999 \
>> -Dsystem-alloc-gid-min=101 \
>> -Dsystem-gid-max=999 \
>> - -Dcreate-log-dirs=false \
>> + ${@ '-Dcreate-log-dirs=false' if oe.types.boolean(d.getVar('VOLATILE_LOG_DIR')) else '' } \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'zeroconf', '-Ddefault-mdns=no -Ddefault-llmnr=no', '', d)} \
>> "
>>
>>
>
> There were recent changes in this area so that is not the correct way
> to do this in master.
>
> meta/conf/bitbake.conf:BB_RENAMED_VARIABLES[VOLATILE_LOG_DIR] = "is obsolete and no longer supported"
>
> This does make me wonder about testing :(.
Guilty as charged. Testing was on scarthgap. I currently does not have a
working test setup for master.
I guess I will have to wait with this until I can do proper testing
then.
I will resend this patch against scarthgap though, as it is valid and
tested there.
For master and styhead, I need to change to check
FILESYSTEM_PERMS_TABLES instead.
/Esben
next prev parent reply other threads:[~2024-10-24 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 11:41 [PATCH] systemd: fix journald persistency when VOLATILE_LOG_DIR is false Esben Haabendal
2024-10-24 12:58 ` [OE-core] " Richard Purdie
2024-10-24 14:29 ` Esben Haabendal [this message]
2024-10-24 22:02 ` Richard Purdie
2024-10-25 6:05 ` Esben Haabendal
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=87seslpoax.fsf@geanix.com \
--to=esben@geanix.com \
--cc=changqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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