On Fri, 19 Feb 2021 at 19:21, intrigeri <intrig...@debian.org> wrote:
> I confirm this problem does not happen when I use "sysctl --system". > However, this problem does happen with procps 2:3.3.17-4 after > a reboot (or more simply, after restarting procps.service). > I'm really not sure why this would matter after 3.3.17-4 as 3.3.16-1 is where the file moved from /etc to /usr/lib but its been protect-links.conf for a while. > My understanding is that when using systemd, what matters is what > systemd-sysctl does, not what "sysctl --system" does: procps.service > Right, you're talking about what the systemd-sysctl does, not the procps sysctl. However the protect-links.conf is in the procps package, hence the bug report is here. So, ignoring the version bit (its the same file) and knowing its the systemd binary makes this a lot clearer. I'll have to look into what happens with changing the name of this file. It's not strictly speaking a conffile but if someone had put a /etc/sysctl.d/protect-links.conf its not going to match anymore. It might be just a matter of putting something into the NEWS as for most people nothing will change. If you (or someone else reading this) has some precedent where a sysctl file in /usr/lib is renamed then I'm happy to hear about it. - Craig
