Red Hat ENTERPRISE 5.4 RELEASE NOTES, Manual

Page: 237 / 466

rhnsd
219
1.194. rhnsd
1.194.1. RHBA-2009:1356: bug fix update
An updated rhnsd package that fixes several bugs is now available.
rhnsd runs periodically to access a Red Hat Network server for software updates.
This updated package applies fixes for the following bugs:
• the rhnsd init script returned incorrect error codes and sometimes prevented correct status
command calls. The init script has been updated so that it returns appropriate error messages, and
the status command call error no longer presents. (
BZ#243699
1509
)
• if a user's system was not registered on the Red Hat Network, the rhnsd postuninstall script would
fail when attempting to upgrade from Red Hat Enterprise Linux 5.3 to Red Hat Enterprise Linux 5.4.
As a result, the rhnsd update would fail. This updated package contains a workaround. To update
the rhnsd package correctly, first uninstall the old version of rhnsd, and then install the new version.
The postuninstall script will then work as expected.(
BZ#503719
1510
)
Users are advised to upgrade to this updated rhnsd package, which resolves these issues.
1.195. rpm
1.195.1. RHBA-2009:1371: bug fix update
Updated rpm packages that resolve several issues are now available.
The RPM Package Manager (RPM) is a command line driven package management system capable
of installing, uninstalling, verifying, querying, and updating software packages.
These updated rpm packages provide fixes for the following bugs:
• on 64-bit multilib systems, verifying all packages on the system led to a large number of files being
listed which only differed in timestamp values. With this update, timestamp differences on multilib
systems are now filtered so that verifying all packages (using the "rpm -Va" command) on both
32-bit and 64-bit systems results in relevant and useful information for system administrators.
(
BZ#426672
1511
,
BZ#472151
1512
)
• verification using the "--root [directory]" option could give false warnings on file ownership due
to using the system's user and group database instead of the alternate root. RPM now performs
verification using actual chrooted environment to ensure the correct user database is used.
(
BZ#434150
1513
)
• in some upgrade scenarios YUM would trigger a massive memory fragmentation in librpm, causing
it to use immoderate amounts of memory. RPM now uses a better allocation algorithm to avoid
excessive fragmentation. In addition, a separate flawed algorithm caused initial installation to
take much longer than it should have. These fixes result in a better-performing RPM overall.
(
BZ#435475
1514
)
• the "rpmbuild" utility silently applied patches that no longer exactly match the source code, which
could cause packaging of unwanted backup files or even result in subtle bugs in the software itself.