reassign -1 linux-sysctl-defaults[...]
thankyou
The procps package doesn't carry any of the sysctl configuration files anymore, but they're in the linux-sysctl-defaults
so reassigning to that package.
linux-sysctl-defaults is meant to provide defaults only. Therefore I
don't think it is appropriate to add that example/template to it.
What is the problem with keeping an example in procps?
<div><br></div><div>It's not going to hurt putting it there, I'm just not sure anyone is going to find it because the</div><div>only reason for an example sysctl file is historical.<br></div><div><br></div><div> - Craig</div><br></div></div>
I think system administrators looking to experiment with sysctl changes
are more likely to reaach for procps and the sysctl command, because:
- sysctl is on the path while systemd-sysctl isn't
- "apt search sysctl" finds procps and not systemd
- A web search for "linux sysctl examples" finds mostly pages mentioning
the sysctl command
On Mon, 26 May 2025 at 02:05, Ben Hutchings <ben@decadent.org.uk> wrote:
linux-sysctl-defaults is meant to provide defaults only. Therefore I don't think it is appropriate to add that example/template to it.
What is the problem with keeping an example in procps?
I can do that, but on a standard Debian system you're not even using the procps sysctl to do the parsing as it is systemd-sysctl in the systemd package doing it.
It's not going to hurt putting it there, I'm just not sure anyone is going to find it because the
only reason for an example sysctl file is historical.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (0 / 16) |
Uptime: | 156:58:45 |
Calls: | 10,384 |
Calls today: | 1 |
Files: | 14,056 |
Messages: | 6,416,474 |