Red Hat Docs  >  Manuals  >  Red Hat Network Manuals  > 

RHN Proxy Server 4.1.0 Release Notes

Copyright © 2006 Red Hat, Inc.

This marks the release of RHN Proxy Server 4.1.0. In addition, Proxy customers will benefit from enhancements made to Red Hat Network as a whole. For this reason, customers are encouraged to also examine RHN Release Notes and the latest RHN Reference Guide available at https://rhn.redhat.com/help/ for changes made to Red Hat Network since the last release of RHN Proxy Server.

General Improvements

  • A bug has been fixed that prevented up2date --get from functioning properly with RHN Proxy Server. Specifically, this bug caused up2date to fail when the --get option was used to retrieve an older version of a package.

  • A bug has been fixed that caused traceback messages to be generated when accessing the /pub/ directory of an RHN Proxy version 3.7.

Improvements to rhnpush

  • A bug that caused rhnpush to fail on Red Hat Enterprise Linux2.1 for Itanium has been addressed.

  • This release addresses a regression that caused rhnpush to be unable to push packages from read-only file systems.

  • Two significant additions to rhnpush's error handling have been made.

    • First, if rhnpush fails to upload a package, it sleeps for 3 seconds before making a second attempt. If the second attempt fails, rhnpush exits with the error code '1'.

    • Second, the --tolerant option has been added to rhnpush. If this option is specified at the command line, rhnpush skips any packages that fail to upload and attempts to push the next file.

  • The rhnpush command now returns a non-zero value when exiting with an error.

  • The rhnpush utility now checks to see if a package already exists on the Satellite before pushing the package. It does this by comparing the MD5 sum of the package on the local system with that of similar packages on the Satellite. If no match exists, the package is pushed to the Satellite.

  • The way rhnpush interacts with its configuration files has been improved. It no longer automatically generates ~/.rhnpushrc and ./.rhnpushrc files whenever rhnpush is called. It does, however, read these files if they exist; the ./.rhnpushrc configuration file has precedence over the ~/.rhnpushrc file.