1RHNPUSH(8) RHNPUSH(8)
2
6 rhnpush - Utility to push binary and source RPMs into an RHN channel.
7
9 rhnpush [ options ... ] [ -v ] [ --verbose ]
10 [ -dDIRECTORY ] [ --dir=DIRECTORY ]
14 [ -cCHANNEL_LABEL ] [ --channel=CHANNEL_LABEL ]
18 [ -nN_HEADERS_PER_CALL ] [ --count=N_HEADERS_PER_CALL ]
22 [ -l ] [ --list ]
26 [ -rRELATIVE_DIRECTORY ] [ --reldir=RELATIVE_DIRECTORY ]
30 [ -oORGANIZATION_ID ] [ --orgid=ORGANIZATION_ID ]
34 [ -uUSERNAME ] [ --username=USERNAME ]
38 [ -pPASSWORD ] [ --password=PASSWORD ]
42 [ -s ] [ --stdin ]
46 [ -Xglob ] [ --exclude=GLOB ]
50 [ --force ]
54 [ --nosig ]
58 [ --newest ]
62 [ --nullorg ]
66 [ --header ]
70 [ --source ]
74 [ --server=SERVER ]
78 [ --new-cache ]
82 [ --extended-test ]
86 [ --test ]
90 [ --tolerant ]
94 [ -h ] [ --help ]
98 [ -? ] [ --usage ]
102
105 The RHN Satellite Package Pusher (rhnpush) pushes RPMs into locally
106 managed channels on an RHN Satellite Server. Refer to the RHN Satellite
107 documentation for further reference.
108
110 -v --verbose
111 Increase verbosity (can use multiple times).
112 -dDIRECTORY
114 process packages from this directory.
115 -cCHANNEL_LABEL,
117 process data for this specific channel (specified by label)
118 only. NOTE: the channel's *label* is NOT the same as the chan‐
119 nel's *name*.
120 -nN_HEADERS_PER_CALL
122 process this number of headers per call. Current default is 25.
123 Must be an integer.
124 -l --list
126 only list the specified channels.
127 -rRELATIVE_DIRECTORY
129 relative directory to associate with each file.
130 -oORGANIZATION_ID
132 Your organization's ID number. Must be an integer.
133 -uUSERNAME
135 username of user that has administrative access to the specified
136 channel.
137 -pPASSWORD
139 see --username.
140 -s --stdin
142 read the package names from standard-in (allows piping).
143 -Xglob exclude packages that matches this glob expression.
145 --force
147 force the package upload (overwrites if package is already
148 uploaded).
149 --tolerant
151 If rhnpush errors while uploading a package, continue attempting
152 to push the rest of the packages.
153 --nosig
155 don't fail if packages are unsigned.
156 --newest
158 push only the packages that are newer than those on the server.
159 Please note that source RPMs are special in that their versions
161 are never compared. Therefore, using this option with RHN Satel‐
162 lite Package Pusher will upload source RPMs for the specified
163 channels only if they were not previously uploaded, and binaries
164 built from them exist in those channels.
165 In other words, you have to upload a binary rpm before being
167 able to use --newest with its source rpm.
168 --nullorg
170 use the null org ID (most often the case).
171 --header
173 only upload the headers.
174 --source
176 the packages indicated are source packages (we treat them dif‐
177 ferently).
178 --server=SERVER
180 push to this server. The format is http[s]://<hostname>/APP
181 --test only print the packages to be pushed, don't actually push them.
183 --new-cache
185 create a new username/password cache
186 --extended-test
188 perform a more verbose test.
189 -h --help
191 briefly describe the options.
192 -? --usage
194 usage summary.
195
197 Rhnpush has three configuration files called /etc/sysconfig/rhn/rhn‐
198 pushrc, ~/.rhnpushrc, and ./.rhnpushrc.
199 /etc/sysconfig/rhn/rhnpushrc is the system-wide default settings for
201 rhnpush.
202 ~/.rhnpushrc is the user-specific settings that override the system-
204 wide settings.
205 ./.rhnpushrc controls the directory specific settings that override the
207 user-specific and system-specific settings.
208 /etc/sysconfig/rhn/rhnpushrc must be present for rhnpush to function
210 correctly. If it is missing, rhnpush will attempt to use a series of
211 default settings stored internally as a replacement. ~/.rhnpushrc and
212 ./.rhnpushrc are not required to be present, but will be used if they
213 are present. They are not created automatically by rhnpush.
214 Rhnpush uses a cache, stored at ~/.rhnpushcache, to temporarily hold
216 the username and password for a user.
217 If the cache is missing, it will be created by rhnpush.
219 If the cache is present and not too old, the usename-password combo
221 will be used as a convenience for the user.
222 The amount of time a cache lasts is configurable in any of the three
224 configuration files.
225 If your username/password combination gets messed up you have two
227 options. One, you can wait until the cache expires, which takes minutes
228 by default. Two, you can use the --new_cache option to force rhnpush to
229 let you reenter your username/password.
230 Using the --stdin and --dir options at the same time works as follows:
232 rhnpush will let you type in rpm names, each rpm name on a separate
233 line. When you have finished entering in rpm names, hit Ctrl-D. Rhnpush
234 will then grab the files from directory you specified with --dir, put
235 them in a list with the rpms you listed through standard input, and
236 send them to the channel that was listed on the command-line or in the
237 configuration files.
238
240 db-control(1) - embedded database environment only!
241 rhn-charsets(8)
243 rhn-schema-version(8)
245 rhn-ssl-dbstore(8)
247 satellite-debug(8)
249 satellite-sync(8)
251 rhn-satellite-activate(8)
253
255 Todd Warner <taw@redhat.com>
256 Mihai Ibanescu <misa@redhat.com>
258Version 2.0 11 August 2010 RHNPUSH(8)