Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP XC System Software : Installation Guide > Chapter 7 Upgrading Your HP XC System

Task 6: Manually Merge Customized Files

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Perform the following tasks to manually merge customizations you made to system configuration files in the previous release that were not merged into the new version of the configuration files:

  1. Use the method of your choice to open and search the /var/log/postinstall.log file for XC specific configuration files that have an .rpmsave extension appended to them. These files contain user customizations that were not merged into the new files in this release. Table 7-5 illustrates how the manual merge process works using the /opt/hptc/systemimager/etc/chkconfig.map file as an example.

    Table 7-5 Merging User Customizations After An Upgrade

    Your Previous Customized Contents Are Contained In This FileYou Merge the Customized Contents Into This File
    chkconfig.map.rpmsavechkconfig.map

     

    The following example uses the grep command to search for the affected files:

    # grep -E .rpmsave /var/log/postinstall.log
  2. Use the method of your choice, such as the diff command, to determine differences between the customized and current versions of configuration files. As software evolves, configuration file formats might change. Carefully compare your original configuration files to the new files before integrating your changes.

  3. Carefully copy customizations from the *.rpmsave version of the file into the new version of the file. Certain *.bak files must also be considered for merging if they have been previously customized.

    Table 7-6 contains a list of XC specific configuration files and standard Linux configuration files that are likely to contain user customizations that you must merge.

    Table 7-6 Files Containing User Customizations

    File NameImportant Notes
    /etc/iptables.proto.bak

    If the head node was previously configured as a NIS slave server, do not merge the nis ports from the iptables.proto.bak file into the iptables.proto file because the nis_server service automatically opens the necessary ports when it is configured during cluster_config processing.

    /hptc_cluster/slurm/etc/slurm.conf.bak 
    /etc/my.cnf.rpmsave 
    /opt/hptc/systemimager/etc/updgi_exclude_file.rpmsave 
    /opt/hptc/systemimager/etc/chkconfig.map.rpmsave 
    /opt/hptc/systemimager/etc/base_exclude_file.rpmsave 
    /opt/hptc/systemimager/etc/*.conf.rpmsave 
    /opt/hptc/config/*.rpmsave 
    /opt/hptc/config/etc/*.rpmsave 

     

  4. Follow the same process to find Linux specific customizations.

    Use the method of your choice to open and search the /root/upgrade.log file for Linux specific configuration files that have either a .rpmsave or a .rpmnew extension appended. This step should only be necessary if you know you changed standard Linux configuration files.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.