On Thu, 31 Oct 2024 at 05:56, Ben Hutchings <b...@decadent.org.uk> wrote:
> On Thu, 2024-10-24 at 21:09 +1100, Craig Small wrote: > > I'm not seeing that. There are three triggers in systemd 256.6-1 but not > > for sysctl files. > > Wouldn't it be in > > > https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/systemd.triggers?ref_type=heads > > This was a proposed action, not a statement of current behaviour. > Ah ok, that's why I can't find them! > - systemd and procps are the only 2 packages that are able to parse and > apply these files. If neither is installed then nothing can be done > with them, so there is little value in adding such a trigger elsewhere. > On reflection, I agree. Both system and procps would have similiar triggers because, as you say, they're the only things that can do something about it. I'm happy to work with the systemd developers to have a consistent set of triggers across both packages. I'd expect the main difference besides what command is run is procps will need some sort of "is systemd running?" check. I am concerned conceptually about setting kernel parameters while the system is out of boot phase. For example setting variables net.ipv4.conf.all/default will do diferent things due to network interfaces that exist, or will exist soon. I don't see a fix for that; after all the issue this report is trying to fix is we want these changes to immediately happen. - Craig
