I'm sorry but I don't understand your answer. I don't see the relevancy of the origin or the contents of the /etc/sysctl.conf file; if that file exists in the system it must be loaded. Otherwise, it's an error.
Apart from Ubuntu installers there are lot's of configuration scripts, installers, applications, etc... that uses /etc/sysctl.conf as it's a method stated in every linux manual or book in the world, or even in the manual page for sysctl.conf shipped by default in Ubuntu. Using etc/sysctl.d/*.conf snippets is an option but not mandatory. Yes, you can place a .conf snippet to /etc/sysctl.d/. But it's not a solution because this should be done every time the /etc/sysctl.conf contents are modified by any means. It implies additional administration work because you need to watch it's future changes to convert it... It's better to just put a symlink and forget about it. So, in my opinion, the bug here is not related to the contents or the origin of /etc/sysctl.conf file. The bug is that systemd-sysctl version 255 effectively loaded /etc/sysctl.conf, as expected, but version 256 don't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084376 Title: [Ubuntu 24.10 Oracular; systemd-sysctl service] File /etc/sysctl.conf is not processed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2084376/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
