A workaround for this that we're using now is to put the sysctl processing into crontab after reboot.
e.g. @reboot root sleep 5 && sysctl --system
Maybe one day someone will fix this bug :)
A workaround for this that we're using now is to put the sysctl processing into crontab after reboot.
e.g.
@reboot root sleep 5 && sysctl --system
Maybe one day someone will fix this bug :)