Description of problem: When doing ifup on an interface, systemd-sysctl appears to fiddle with my sysctl settings without telling me what setting, why it happens, how it is changing. This without asking or explaining why. Version-Release number of selected component (if applicable): systemd-204-18.fc19.i686 How reproducible: See below. Steps to Reproduce: See below. Actual results: # ifup eth1.6 Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.conf'. Expected results: # ifup eth1.6 # Additional info: If there is a need for systemd doing even more stuff than init ever did, please make it even more clear why that is needed, how it works, how it can be configured and how it can be turned off. As the simplest of changes take ages to complete (swapping, logging, etc) I know what I am in for.
The network interface specific sysctl options are applied when the network interfaces show up. This is necessary to make sure they are applied without races, as applying them solely at early boot would not work because there's no guarantee that the interfaces have shown up at that point and hence whether they would be applied at all. It is ture that this behaviour is currently not documented. I have now made a change to git accordingly. http://cgit.freedesktop.org/systemd/systemd/commit/?id=8f03fd08911016d8bbcad5892b2c07b30a4c2306
How did we ever get by without this?
systemd-204-20.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/systemd-204-20.fc19
Package systemd-204-20.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-204-20.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-8761/systemd-204-20.fc19 then log in and leave karma (feedback).
systemd-204-20.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.