8.210. sapconf

Bug Fixes

BZ#1024356

In certain situations, the sapconf script created the /etc/hosts file in an incorrect format, thus the file did not return the fully qualified domain name (FQDN). As a consequence, SAP installation failed unexpectedly. With this update, the script has been edited to handle situations when the incorrect /etc/hosts file was created. In addition, when FQDN is not returned properly, the script exits with the error code 4.

BZ#1025187

Previously, the manual page for the sapconf script was missing. This update adds the missing manual page to the sapconf package.

BZ#1040617

Due to a bug in the underlying source code, the sapconf script was unable to verify if a virtual guest was a VMware guest. Consequently, an attempt to use sapconf on such a guest failed. With this update, sapconf recognizes the VMware guests as expected.

BZ#1051017

The order of reading limit files in Red Hat Enterprise Linux is as follows: First is read the /etc/security/limits.conf file and then the limit files located in the /etc/security/limits.d/ directory according to the C localization functions. When an entry is specified in two or more files, the entry that is read last takes effect. Previously, the sapconf script wrote entries to /etc/security/limits.conf, which could cause the sapconf entries to be overwritten by the same entries in files located in /etc/security/limits.d/. With this update, a separate sapconf limit file has been added to /etc/security/limits.d/ to anticipate this bug.

BZ#1083651

When the sapconf script updated the /etc/hosts file, permissions of that file were incorrectly modified. This update applies a patch to fix this bug, and sapconf no longer overwrites the file's permissions.