Red Hat NETWORK 4.0 -, Reference Manual

Page: 151 / 290

Chapter 6. Red Hat Network Website 135
(
rhncfg-client
), the variables will be replaced with the hostname and IP address of the
system, as recorded in RHN’s System Profile. In the above configuration file, for example,
the deployed version resembles the following:
hostname=test.example.domain.com
ip_address=177.18.54.7
To capture custom system information, insert the key label into the custom information
macro (rhn.system.custom_info). For instance, if you developed a key labeled "asset" you
can add it to the custom information macro in a configuration file to have the value substi-
tuted on any system containing it. The macro would look like this:
asset={@ rhn.system.custom_info(asset) @}
Upon deployment of the file to a system containing a value for that key, the macro gets
translated, resulting in a string similar to the following:
asset=Example#456
To include a default value, for instance if one is required to prevent errors, you can append
it to the custom information macro, like so:
asset={@ rhn.system.custom_info(asset) =
’Asset #’ @}
This default is overridden by the value on any system containing it. For
instructions on developing custom system information keys, refer to
Section 6.4.9 Custom System Info — .
Using the Red Hat Network Configuration Manager (
rhncfg-manager
) will not trans-
late or alter files, as that tool is system agnostic. Binary files cannot be interpolated.
6.7. Schedule
If you click the Schedule tab on the top navigation bar, the Schedule category and links
appear. These pages enable you to track the actions taking place within your systems. An
action is a scheduled RHN task that is to be performed on one or more client systems. For
example, an action can be scheduled to apply all Errata Updates to a system.
Red Hat Network keeps track of the following action types:
1. Package Alteration (installation, upgrade, and removal)