[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1085160: linux-sysctl-defaults: apply setting after installation





On Thu, 24 Oct 2024 at 11:25, Ben Hutchings <ben@decadent.org.uk> wrote:

1. As discussed in the GitLab MR, systemd implements a file trigger on
   sysctl configuration files.
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

2. Either:
   (a) procps implements a similar trigger, but makes it a no-op when
       systemd is pid 1.
   (b) linux-sysctl-defaults postinst does:
       - if systemd is pid 1, nothing;
       - otherwise, if sysctl is installed, "sysctl --system";
       - otherwise, nothing.
I agree that directly calling the specific file is a bad idea. A user may have overrides in other files
which may not be caught up if you specify a file directly.

So there are a few things here:
 * A fix for linux-sysctl-defaults conf files
* Generically something for any package

If we're trying to do the first, then having something like your option b seems a good idea.
The conf file and the postinst are the same package, so its simple. It is actually what
#1085160 is about.

Should something, procps or linux-sysctl-defaults, be watching the sysctl.d files
in their various locations and triggering a sysctl if they change? Or should the 
individual packages do it?

Should there be some small script that works out which sysctl to use?
If there is 'whatever-sysctl-is-here' script, where should it live?
Or would some wiki entry do it better?

 - Craig


Reply to: