Bug 2111915 - Backport: sysctl: config directory order
Summary: Backport: sysctl: config directory order
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: procps-ng
Version: 8.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jan Rybar
QA Contact: Karel Volný
Šárka Jana
Depends On:
TreeView+ depends on / blocked
Reported: 2022-07-28 12:55 UTC by Jan Rybar
Modified: 2022-11-08 12:19 UTC (History)
2 users (show)

Fixed In Version: procps-ng-3.3.15-8.el8
Doc Type: Enhancement
Doc Text:
.`sysctl` now matches the `systemd` directory order The configuration directory order of the `sysctl` utility is now synchronized with the `systemd-sysctl` directory order. The configuration directory examines and changes kernel parameters at runtime. The configuration files in `/etc/sysctl.d` directory have higher priority than configuration files in `/run/sysctl.d`, and no more disruptions to the precedence of files between `sysctl` and `systemd` happen.
Clone Of:
Last Closed: 2022-11-08 10:43:42 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-129457 0 None None None 2022-07-28 14:06:46 UTC
Red Hat Product Errata RHBA-2022:7687 0 None None None 2022-11-08 10:43:47 UTC

Description Jan Rybar 2022-07-28 12:55:44 UTC
Description of problem:
The order of configuration directories was changed in upstream [1]. This change is now in CentOSStream and RHEL9. There is a request to make this alignment with systemd-sysctl order also in RHEL8.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:
Configs in /run/sysctl.d have higher priority than configs in /etc/sysctl.d

Expected results:
Configs in /etc/sysctl.d are preferred over the ones in /run/sysctl.d

Additional info:
[1] https://gitlab.com/procps-ng/procps/-/commit/24a1574f0acbe636c98ab13b439c93f7b91de697

Comment 6 errata-xmlrpc 2022-11-08 10:43:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (procps-ng bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.