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.

Description of problem:
closely related to 663594 - [RFE] 

in short, these .conf files have been deemed not-configuration-files, and are handled as such by rpm (similar to the /etc/init.d/ scripts). Instead, .override files should be used.

Unfortunately, the suffix of the files is obviously misleading, and the way to use the .override files (and the fact this functionality exists) is not immediately obvious.

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

upstart in RHEL6.3

How reproducible:

n/a

Steps to Reproduce:
1.
2.
3.
  
Actual results:

user assumes these are configuration files, edits them, and finds them to be overwritten  at next upgrade by the files inside the rpm.

Expected results:

user immediately notices these are not config files, and not meant to be edited.

Additional info:

the simple solution is to not name the files .conf, to begin with, and add a warning inside such files of the sort "do NOT edit, your changes will be overwritten. Please see man 5 foo.override on how to use .override files instead"

It is not a good idea to change suffix of these files, but adding some comment with warning looks as a reasonable solution.

*** Bug 1020904 has been marked as a duplicate of this bug. ***

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.

http://rhn.redhat.com/errata/RHBA-2013-1679.html