Red Hat NETWORK 3.5 - PROVISIONING, Reference Manual

Page: 62 / 136

52 Chapter 4. Red Hat Network Website
tions. Once the key exists, you may assign a value to it by clicking create new value here. Click
the name of the key in the resulting list and enter a value for it in the Description field, such as
"Cube #456." Then click the Update Key button.
•
Reactivation
— A System Profile-specific activation key. This allows you to create an activation
key encompassing this system’s ID, history, groups, and channels. You may then use this key
only once with the
rhnreg_ks
command line utility to re-register this system and regain all
Red Hat Network settings. Refer to Section 2.5 Registering with Activation Keys for instructions.
Unlike typical activation keys, which are not associated with a specific system ID, keys created
here do not show up within the Activation Keys page.
Warning
When kickstarting a system with its existing RHN profile, it will use the system-specific activation
key created here to reregister the system and return its other RHN settings. For this reason, you
should not regenerate, delete, or use this key (with
rhnreg_ks
) while a profile-based kickstart
is in progress. If you do, the kickstart will fail.
•
Remote Command — The method for running a remote command on the system. To allow
remote commands to be run on the client through RHN, first install the latest
rhncfg*
pack-
ages available within the RHN Provisioning child channel for the system. These may already be
installed if you kickstarted the system with configuration management functionality.
Next, create the necessary directory on the target system:
mkdir -p /etc/sysconfig/rhn/allowed-actions/script
Then create a
run
file in that directory to act as a flag to RHN signaling permission to allow
remote commands:
touch /etc/sysconfig/rhn/allowed-actions/script/run
You may then identify a specific user, group, and timeout period, as well as the script itself on
this page. Select a date and time to begin attempting the command, and click
Schedule Remote
Command
.
•
Connection — The system’s path to the package repository. Regardless of whether your client
systems receive updates from the central RHN servers or an RHN Satellite Server, it is important
to know if packages are being routed through any RHN Proxy Servers. This subtab identifies the
proxies being used and the order in which they receive updates. A one (1) indicates the top proxy
connected to either RHN or a satellite. If no proxy is used, you receive a message stating, "This
system connects directly and not through a proxy."
•
Errata
— Contains a list of Errata Alerts applicable to the system. To apply updates, select them
and click the Apply Errata button. Double-check the updates to be applied on the confirmation
page, then click the
Confirm
button. After confirming, the action is added to the
Pending Actions
list under Schedule . Errata that have been scheduled cannot be selected for update. In the place of
a checkbox, you will find a clock icon that, when clicked, takes you to the
Action Details
page.
To help users determine whether an update has been scheduled, a Status column exists within the
Errata table. Possible values are: None, Pending, Picked Up, Completed, and Failed. This column
identifies only the latest action related to an Errata. For instance, if an action fails and you resched-
ule it, this column will show the status of the Errata as Pending only (with no mention of the
previous failure). Clicking a status other than None takes you to the Action Details page. This
column corresponds to one on the
Affected Systems
tab of the
Errata Details
page.
•
Packages — Manages the packages on the system.
•
Packages — The default display of the Packages tab describes the options available to you and
provides the means to update your package list. If after exploring the packages, you believe the
list is outdated or incomplete (or you installed the packages manually and did not have RHN
install them), click the
Update Package List
button on the bottom right-hand corner of this