Bug#864341: systemd-sysctl: failed to apply sysctl config at bootup

[Arturo Borrero Gonzalez]

On Wed, 7 Jun 2017 13:35:13 +0200 Moritz Muehlenhoff <jmm at debian.org> wrote:

> A couple of possible solutions, but these are all rather something for
> upstream development:
> - sysctl.conf files could gain an additional parameter which specifies
>   the kernel module creating the sysctl. systemd-sysctl could then
>   trigger the loading of that module and wait until the specified sysctl
>   is present (I think that's the cleanest solution)
> - All sysctl settings should be entirely idempotent. systemd-sysctl could
>   be re-run in multi-user.target (fairly ugly)
> - Or maybe split off a separate systemd-sysctl-stage2.service, which reads
>   a separate sysctl config (which can then be used for driver which are loaded
>   late)
>

Hi,

I'm fine with any of them.
It would be great if systemd maintainers could comment on the solutions.

By now, I'm using /etc/modules-load.d/ which seems to work in my
concrete case. But I understand
that my enviroment doesn't seem to manifest the race condition
(between sysctl and modules) and this is not a robust solution.