Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES Instrukcja Użytkownika Strona 29

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 38
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 28
Configuring and Using the RHN Package Manager
25
rhn_package_manager -l -c name_of_private_channel
The -l option lists the package name, version number, release number, architecture, and channel
name for each package in the specified channel(s). Refer to Table 6.1, “rhn_package_manager
options” for additional options.
Table 6.1, “rhn_package_manager options” is a summary of all the command line options for RHN
Package Manager (rhn_package_manager):
Table 6.1. rhn_package_manager options
Option Description
-v, --verbose Increase verbosity of standard output messages.
-d, --dir DIRECTORY_NAME Process packages from this directory.
-c, --channel CHANNEL_NAME Specify the channel to receive packages. Multiple channels
may be specified using multiple instances of -c (e.g.: -c
channel_one -c channel_two)
-n, --count NUMBER Process this number of headers per call — the default is
32.
-l, --list List the packages in the specified channel(s).
-s, --sync Check if local directory is in sync with the server.
-p, --printconf Print the current configuration and exit.
--newest Push only the packages that are newer than those on
the server. Note that source packages are special in
that their versions are never compared to each other.
Their newness is dependent on their associated binary
packages. Using this option with RHN Package Manager
and just a source package does upload the package, but
the source package does not appear in the RHN Web
interface until the associated binary package has been
uploaded. Contrast this with --source. Using --source
--newest together does update the stand-alone source
package with newer packages and does not require an
associated binary package to be uploaded first.
--source Upload the indicated source packages. Doing this treats
them as plain, stand-alone packages and not as special
source packages associated with another, pre-existing
binary package. For example, you can use this when you
want to distribute application source to developers and
testers outside of regular source control management.
--stdin Read the package names from standard input.
--nosig Don't fail if packages are unsigned.
--no-ssl Turn off SSL (not recommended).
--stdin Read the package names from standard input.
--username USERNAME Specify RHN username. If not provided, you are prompted
for the username of a valid Channel Administrator.
--password PASSWORD Specify RHN password. If not provided, you are prompted
for the password of a valid Channel Administrator.
Przeglądanie stron 28
1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 37 38

Komentarze do niniejszej Instrukcji

Brak uwag