Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES Manual de usuario descargar pdf (Pagina 28)

Chapter 6. Uploading and Maintaining Custom Packages

Tip

Create at least one private channel to receive custom packages prior to upload into Red Hat

Network, since a channel is required for systems to obtain the packages.

The following command uploads the package headers to the RHN Servers and copies the packages to

the RHN Proxy Server repository:

rhn_package_manager -c label_of_private_channelpkg-list

The label_of_private_channel is the custom channel created to receive these packages. Be

sure you use the precise channel label specified during its creation. If you have one or more channels

specified (using -c or --channel), the uploaded package headers are linked to all the channels

identified. If you do not specify a channel, the packages are deposited in the No Channels section of

the Package Management page. Refer to Section 4.6, “Assigning Packages to Software Channels”

for instructions on reassigning packages.

The pkg-list reference represents the list of packages to be uploaded. These packages must

already be physically copied to the Proxy host. Alternatively, use the -d option to specify the local

directory that contains the packages to be added to the channel. RHN Package Manager can also

read the list of packages from standard input (using --stdin).

Other options are specified in a configuration file, such as the Red Hat Network Server URL, the HTTP

proxy username and password (if your HTTP proxy requires authentication), and the top directory

where packages live. This special configuration must not be edited and is located at /etc/rhn/

default/rhn_proxy_package_manager.conf. You can override the choices in that default

configuration file with settings in the main configuration file /etc/rhn/rhn.conf or via command

line options passed to RHN Package Manager.

Parameters not set in this file are read from .rhn_package_manager in the home directory of the

user currently logged in and finally from /etc/rhn/rhn_package_manager.conf. Make sure all of

these files have the appropriate permissions to prevent others from reading them.

After uploading the packages, check to see if the local directory is in sync with the RHN Server's

image of the channels:

rhn_package_manager -s -c name_of_private_channel

This -s option lists all the missing packages, which are packages uploaded to the RHN Server but

not present in the local directory. You must be an Organization Administrator to use this option. The

application prompts you for your RHN username and password.

The --copyonly option copies the file listed in the argument into the specified channel without

uploading to the Satellite. This is useful when a channel on a RHN Proxy Server is missing a package

and you don't want to reimport all of the packages in the channel.

rhn_package_manager -c channel-name --copyonly /path/to/missing/file

You can also use RHN Package Manager to retrieve a list of packages in a channel, as they are

stored by the RHN Server:

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 37 38

Sin comentarios

Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES Manual de usuario Pagina 28