Dear Maintainer,

Since clean-up of /etc/sysctl.conf file in favor of sysctl.d/*.conf,
the original sysctl.conf template under /usr/share/doc/procps/examples/ is also gone.

Please consider adding it back or create some form of new one as example/template,
as the previous one are so useful especially from networking/routing/firewall prespective,
one almost only need to uncomment few # and call it a day.
The orignal one also serve as a great reminder & starting point for
security tuning, the clearness is still better than "sysctl -a" with pattern filtering.

BR,
Kevin

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-base folk, if you need the last version of sysctl.conf the commit to
remove it was at
https://salsa.debian.org/debian/procps/-/commit/77f54cb9d9951b193d2aaeb694e56061309eb3ef

 - Craig

[...]

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?

Ben.

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.

 - Craig

I'm well aware of that.

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

Ben.

reassign -1 procps
thankyou
That seems fair enough, I'll put them into procps.

 - Craig