
Configuring the RHN Push Application
27
Table 6.2. rhnpush options
Option Description
-v --verbose Increase verbosity, option can be used multiple times, that
is, -vv, -vvv, and so forth.
-d, --dir DIRECTORY Process packages from this directory.
-c, --channel CHANNEL_LABEL Specify the channel to receive packages. Note that
this is required and is not the same as the channel's
name. Multiple channels may be specified using
multiple instances of -c (e.g. -c=CHANNEL_ONE -
c=CHANNEL_TWO).
-n, --count
N_HEADERS_PER_CALL
Process this number of headers per call. Must be an
integer. The default number is 25.
-l, --list List only the specified channels.
-r, --
reldirRELATIVE_DIRECTORY
Associate this relative directory with each file.
-o, --orgidORGANIZATION_ID Include your organization's ID number. Must be an integer.
-u , --username USERNAME Include the RHN username of the user that has
administrative access to the specified channel. If not
provided, rhnpush prompts for the username of a valid
Channel Administrator. The username and password
are cached in ~/.rhnpushcache for a limited time, five
minutes being the default. Use --new-cache to force a
new username and password.
-p , --password PASSWORD Include RHN password of user that has administrative
access to the specified channel. If not provided,
rhnpush prompts for the password of a valid Channel
Administrator. The username and password are cached in
~/.rhnpushcache for a limited time, five minutes being
the default. Use --new-cache to force a new username
and password.
-s, --stdin Read package list from standard input, for example from a
piped ls command.
-X, --exclude GLOB Exclude packages that match this glob expression.
--force Force upload of a package, even if a package of that name
and version currently exists in the channel. Without this
option, uploading a pre-existing package returns an error.
--nosig Don't fail if packages are unsigned.
--new-cache Forces RHN Push to drop the username and password
cache, then accept or ask for new ones. This is useful if
you make a mistake entering them the first time.
--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 Push 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.
Comentarios a estos manuales