Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Справочное руководство

Страница: 145 / 318

Locally-Managed Files
133
Note
By default, the maximum file size for configuration files is 128KB. If you need to change
that value, find and modify the following line in the
/etc/rhn/default/rhn_web.conf
file:
web.maximum_config_file_size=128
You must also find and change the following line in the
/etc/rhn/default/
rhn_server.conf
file to the same value:
maximum_config_file_size=128
Change the value in both files from
128
to the desired value in kilobytes.
7.7.4.1. Centrally-Managed Files
Centrally-managed files are those that are available to multiple systems. Changing a file within a
centrally-managed channel may result in changes to several systems.
This page lists all files that are currently stored in your central configuration channels. Click on the
Path
of a file to be taken to the
Configuration File Details
page for that file. Select the name of
the configuration channel to be taken to the
Channel Details
page of the channel that contains
the file. Clicking on the number of systems takes you to a listing of systems currently subscribed to
the channel containing that file. Finally, clicking on the number of overriding systems displays a list
of systems that have a local (or override) version of the configuration files (which means that the
centrally-managed file will not be deployed to those systems.)
7.7.5. Locally-Managed Files
Locally-managed configuration files are those files that apply to only one system. They may be
files in the system's sandbox or they may be files that can be deployed to the system at any time.
Local files have higher priority than centrally-managed files - that is, if a system is subscribed to a
configuration channel with a given file, and also has a locally-managed version of that same file, the
locally-managed version is the one that will be deployed.
This page lists all of the local (override) configuration files for your systems. This includes the local
configuration channels and the sandbox channel for each Provisioning-entitled system.
Click the
Path
of the file to go to the
Config File Details
page for the file. Click the name of the
system to which it belongs to go to the
System Details
�
Configuration
�
Configuration
�
Overview
page for the system.
7.7.5.1. Including Macros in your Configuration Files
Being able to store and share identical configurations is useful, but what if you have many variations
of the same configuration file? What do you do if you have configuration files that differ only in system-
specific details, such as hostname and MAC address?