Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #84435

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

From Craig Small <csmall@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1085160: linux-sysctl-defaults: apply setting after installation
Date 2024-11-04 11:50 +0100
Message-ID <JF2OK-6y5W-25@gated-at.bofh.it> (permalink)
References (1 earlier) <JATAl-3MZc-1@gated-at.bofh.it> <JB3gm-3SMN-3@gated-at.bofh.it> <JDmeR-5qBG-17@gated-at.bofh.it> <JxSAN-1Pjy-3@gated-at.bofh.it> <JDmeR-5qBG-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, 31 Oct 2024 at 05:56, Ben Hutchings <ben@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

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1085160: linux-sysctl-defaults: apply setting after installation sergio <sergio+it@outerface.net> - 2024-10-15 18:30 +0200
  Processed: Re: Bug#1085160: linux-sysctl-defaults: apply setting  after installation "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-10-18 23:10 +0200
  Bug#1085160: linux-sysctl-defaults: apply setting after installation Noah Meyerhans <noahm@debian.org> - 2024-10-18 23:10 +0200
  Bug#1085160: linux-sysctl-defaults: apply setting after installation Ben Hutchings <ben@decadent.org.uk> - 2024-10-24 02:10 +0200
    Bug#1085160: linux-sysctl-defaults: apply setting after installation Craig Small <csmall@debian.org> - 2024-10-24 12:30 +0200
      Bug#1085160: linux-sysctl-defaults: apply setting after installation Ben Hutchings <ben@decadent.org.uk> - 2024-10-30 20:10 +0100
        Bug#1085160: linux-sysctl-defaults: apply setting after installation Craig Small <csmall@debian.org> - 2024-11-04 11:50 +0100
  Processed: Re: Bug#1085160: linux-sysctl-defaults: apply setting  after installation "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-10-24 02:10 +0200
  Processed: Re: linux-sysctl-defaults: apply setting after  installation "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-11-25 00:30 +0100
  Bug#1085160: linux-sysctl-defaults: apply setting after installation Ben Hutchings <ben@decadent.org.uk> - 2024-11-25 00:30 +0100

csiph-web