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:
As per : https://bugzilla.redhat.com/show_bug.cgi?id=184820

In RHEL5, shmmax and shmall were set to the theoretical limit of the architecture, which for x86_64 was 64G and 4G respectively. RHEL6 doesn't have these set.

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

initscripts-9.03.17-1.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Compare /etc/sysctl.conf in RHEL5 and RHEL6

  
Actual results:
shmmax and shmall reverts back to the defaults set in RHEL3/4

Expected results:
shmmax and shmall should be set the same way it was done in RHEL5

Additional info:

If it was intentionally reverted, I couldn't find the reasons to do so.

It wasn't really an intentional change; it was a RHEL 5 change that we forgot to pull forward. CC'ing some more people for discussion of the impact.

Created attachment 476993 [details]
set default shmmax and shmall for certain architectures

This patch is adapted from RHEL-5 branch (http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=00b168f895a662adb0cecb12e8d619778f35f633)

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0647.html