
Chapter 6. Uploading and Maintaining Custom Packages
26
Option Description
--dontcopy In the post-upload step, do not copy the packages to their
final location in the package tree.
--copyonly Only copy the packages, do not re-import them.
--test Only print a list of the packages to be pushed.
-?, --help Display the help screen with a list of options.
--usage Briefly describe the available options.
--copyonly Only copy packages
Tip
These command line options are also described in the rhn_package_manager manual page:
man rhn_package_manager.
6.2. Uploading Packages to RHN Satellite Server
The RHN Push application allows you to serve custom packages associated with a private RHN
channel through the RHN Satellite Server. If you want the RHN Satellite Server to serve only official
Red Hat Enterprise Linux packages, you do not need to install RHN Push.
To use RHN Push, install the rhnpush package and its dependencies. This package is available to
registered RHN Satellite Server systems and is installed by running up2date rhnpush.
RHN Push uploads RPM header information to the RHN Satellite Server database and places the
RPM in the RHN Satellite Server package repository. Unlike the RHN Proxy Server's RHN Package
Manager, RHN Push never distributes package information, even the headers, beyond the RHN
Satellite Server database.
Tip
If your Satellite installation is enabled to support Solaris OS systems, you may use RHN Push
from a Solaris client to upload Solaris package content to custom Solaris channels.
6.2.1. Configuring the RHN Push Application
When RHN Push is installed, a central configuration file is installed in /etc/sysconfig/rhn/
rhnpushrc. This file contains values for all the options contained in Table 6.2, “rhnpush options”.
These distinct configuration files are useful in varying your settings depending on the directory from
which the rhnpush command is issued. Settings in the current directory (./.rhnpushrc) take
precedent over those in the user's home directory (~/.rhnpushrc), which are used before those in
the central configuration file (/etc/sysconfig/rhn/rhnpushrc).
For instance, you can use the current directory configuration file to specify the software channel to be
populated, the home directory configuration file to include the username to be invoked, and the central
configuration file to identify the server to receive the packages.
Table 6.2, “rhnpush options” contains all command line options for the rhnpush command:
Comentarios a estos manuales