Manage Config Channels - Red Hat NETWORK 3.6 Reference Manual

Chapter 6. Red Hat Network Website
6.6.5.3.1.4. Package Details
A list of the files that comprise this package, including their MD5 Sums and sizes. (This information
is similar to issuing the command
6.6.5.3.2. Package Details
List of newer versions of the packages released via Errata Alerts.
6.6.5.3.3. Package Details
List of systems with this package installed.
6.6.5.3.4. Package Details
List of systems on which the package can be installed. Go here to install packages on entitled systems.
Refer to Section 6.6.5.1 Software Package Install for instructions.
6.6.6. Manage Config Channels —
Provides the means to create and oversee channels containing configuration files. Like software chan-
nels, configuration channels store files to be installed on systems. Unlike software packages, various
versions of configuration files may prove useful to a system at any given time. Further, RHN allows
you to include variables, or macros, that may make your configuration files templates that can be
deployed across your organization, with the relevant values populated upon individual system instal-
lation.
6.6.6.1. Preparing Systems for Config Management
For a system to have its configuration managed through RHN, it must have the appropriate tools and
config-enable file installed. These tools may already be installed on your system, especially if you
kickstarted the system with configuration management functionality. If not, they can be found within
the RHN Provisioning child channel for your distribution. Download and install the latest
packages.
Next, you must place a config-enable file on the system to have config actions scheduled. This file is
required to allow configuration management on the system while preventing inadvertent and poten-
tially dangerous changes. To create this file, issue the following commands as root. First, create the
necessary directory:
mkdir -p /etc/sysconfig/rhn/allowed-actions/configfiles
Then, you should decide exactly what actions should be allowed by system administrators. The fol-
lowing modes are available:
deploy — Install configuration files from the central repository on the system. Without this set, the
•
configuration management interface provides no real value for this system.
verify — Identify any differences between configuration files on the system and those associated
•
with it in the central repository.
Details File List
rpm -ql packagename
Newer Versions
Installed Systems
Target Systems —
.)
103
rhncfg*