sysctl.d file is misnamed and unneeded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
procps (Ubuntu) |
Fix Released
|
Low
|
Dan Streetman | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Hirsute |
Won't Fix
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[impact]
the sysctl.d file /usr/lib/
Additionally, this file should not be included at all, as (unlike Debian) Ubuntu assumes systemd will always be installed, thus the sysctl settings from this file will be provided by the systemd-provided sysctl config files.
[test case]
create a file, e.g. /etc/sysctl.
[regression potential]
any regression would likely result in incorrect or unexpected values for the sysctls contained in this conf file
[scope]
this is needed in f and later
this file is not present in b
however, see other info
[other info]
while this bug exists in f and later, it's also trivial to work around it (though not obvious) by renaming the manual configuration file, e.g. instead of using /etc/sysctl.
Since removing the file entirely could result in a change in behavior, if the local admin has explicitly modified the file or taken other steps, and since it's trivial (though again, not obvious) to override the file lexically, this seems like it should not be SRUed, but only fixed in the development release.
Also, since Debian's policy does allow for systems that do *not* use systemd, I'm not opening a bug against Debian to remove the file.
For clarity, I explicitly added SRU release targets and marked them as either invalid (for bionic, since the file doesn't exist there) or wont-fix (as explained in the description).