I fixed a bug in systemd where its binaries would output to the journal
instead of stdout when invoked as a child process by pacman. This output
was always there, you just didn't see it until now because it went to the
journal instead of stdout. I get the same messages so I wouldn't worry
about it.
Cheers,
Daan
On Sat, Aug 22, 2020, 5:12 AM David C. Rankin <
drankina...@suddenlinkmail.com> wrote:
> Arch devs,
>
> For the past several updates, I have noticed the kernel sysctl settings
> messages saying:
>
> ( 5/17) Applying kernel sysctl settings...
> Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
> Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
> Not setting net/ipv4/conf/all/accept_source_route (explicit setting
> exists).
> Not setting net/ipv4/conf/default/accept_source_route (explicit setting
> exists).
> Not setting net/ipv4/conf/all/promote_secondaries (explicit setting
> exists).
> Not setting net/ipv4/conf/default/promote_secondaries (explicit setting
> exists).
>
> After the recent netctl message issue, I want to nail down what set
> these in
> /proc and whether it is something I need to do something about. I didn't
> set
> any of these specifically, so I presume they are either explicit settings
> made
> during the kernel build or they were set somewhere long ago by some
> previous
> Arch default. In either case, if there were no issues, I wouldn't expect
> pacman to go out of its way to tell me about them if nothing needs to be
> done.
>
> Though I can also see the messages just being some default behavior of
> whatever the kernel sysctl hook is warning about choices that are
> explicitly set.
>
> Do I need to do anything about these?
>
>
> --
> David C. Rankin, J.D.,P.E.
>
