Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBranislav Náter
2015-04-29 13:55:33 UTC
Description of problem:
During testing of bz#1120580 I've found out, that if configuration files have the same name, only one (the one with higer priority?) file is processed.
Version-Release number of selected component (if applicable):
procps-3.2.8-33.el6
How reproducible:
always
Steps to Reproduce:
1. create configuration file with the same name in different system directory (/etc/sysctl.d/ and /run/sysctl.d/)
# cat /etc/sysctl.d/test.conf
vm.swappiness=60
# cat /run/sysctl.d/test.conf
vm.stat_interval=2
2. run sysctl --system
Actual results:
* Applying /run/sysctl.d/test.conf ...
vm.stat_interval = 2
#
Additional info:
If the configuration files have different names, both are applied (even if they have the same values):
* Applying /run/sysctl.d/test1.conf ...
vm.swappiness = 60
* Applying /etc/sysctl.d/test2.conf ...
vm.swappiness = 60
After the quick discussion with devel it seems to be expected behaviour. Then this should be explained in man pages. Current description in man pages is:
--system
Load settings from all system configuration files.
/run/sysctl.d/*.conf
/etc/sysctl.d/*.conf
/usr/local/lib/sysctl.d/*.conf
/usr/lib/sysctl.d/*.conf
/lib/sysctl.d/*.conf
/etc/sysctl.conf
This issue is fixed in new sysctl in procps-ng as the new version takes systemd into account and manpage is rewritten. Hence this issue is RHEL6 specific and will not be proposed to upstream. However it can be fixed as easyfix.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0769.html