Red Hat ENTERPRISE LINUX 5.5 - S 2010, Manual

Page: 30 / 470

Chapter 1. Package Updates
20
* the chkconfig(8) man page contained a description of the syntax for running chkconfig that differed
from the correct description presented when running "chkconfig --help". The man page has been
corrected to correspond with the program's help information. (
BZ#501225
110
)
* the chkconfig(8) man page contained an incorrect reference to runlevel 7, which does not exist
(runlevels extend from 0 to 6, inclusive). This update corrects the man page by removing all
references to "runlevel 7". (
BZ#466740
111
)
* the ntsysv(8) man page referenced a non-existent man page, servicesconf. This reference has been
removed. (
BZ#516599
112
)
All users of chkconfig are advised to upgrade to these updated packages, which resolve these issues.
1.19. cman
1.19.1. RHBA-2009:1435: bug fix update
Note
This update has already been released (prior to the GA of this release) as errata
RHBA-2009:1435
113
Updated cman packages that fix a bug and add an enhancement are now available.
The Cluster Manager (cman) utility provides user-level services for managing a Linux cluster.
This update applies the following bug fix:
* in several places internally, cman assumed a transition message meant the node in question (or
the sending node) was joining the cluster rather than just sending its current post-transition state. In
some circumstances, this could lead to cman killing the wrong nodes. With this update, cman now
checks the first_trans flag, which is set when a node first encounters another node in the cluster. Only
if first_trans is set does cman now consider the node as joining the cluster. (
BZ#518061
114
)
Also, this update includes the following enhancement:
First, if a node was asked to remove a key (fence) for a device that it was not registered with, the node
attempted to register with that device on-the-fly. With this update, when nodes are asked to remove a
key from devices with which they are not registered, the fencing fails.
Second, for the common case of SAN environments with multiple Logical Unit Numbers (LUNs),
the devices (LUNs) that can be unregistered must be ordered consistently on all nodes. Consistent
ordering is not guaranteed by the Logical Volume Manager (LVM), however; device names can vary
from node to node to prevent interleaving of fence operation among devices. With this update, the
fence_scsi agent extracts the device name (pv_name) and Universally Unique Identifier (pv_uuid) and
builds a hash keyed on the UUID (which is consistent on all nodes). This ensures devices are ordered
consistently on each node.
110
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=501225
111
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=466740
112
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=516599
114
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=518061