1. Feature Overview:
Feature Id: 
a. Name of Feature: [6.0 FEAT] Update request for Servicelog
b. Feature Description
libservicelog packages are currently present in RHEL6, but the servicelog package, which uses this
library, is not. This is a request to add the 32-bit version of this package. 64-bit version is
not needed at this time, but might be included as well, to meet Distro partner policy for RHEL6
2. Feature Details:
Sponsor: LTC RAS
Arch Specificity: purely arch specific code
Affects Kernel Modules: No
Delivery Mechanism: Direct from Community
Category: system management
Request Type: Toolchain - Enhancement from Upstream
d. Upstream Acceptance: No Code Required
Sponsor Priority P2
f. Severity: high
IBM Confidential: No
Code Contribution: IBM code
g. Component Version Target:
3. Business Case
Some third party applications, such as IBM Director, require servicelog in order to access and
modify system events, such as hardware errors or maintenance such as adapter replacements.
Servicelog is essential for the smooth management of a Power server, using Director.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Michael W. Wortman, firstname.lastname@example.org
NAREN A. DEVAIAH, email@example.com
BRAD PETERS <firstname.lastname@example.org> -
Request for servicelog update from current, validated version (1.0.1) to latest available, 1.1.7,
available from .
v1.1.x introduced a merged API, combining that of the 0.2.9 and 1.0 API's. This merged API was
requested by IBM Director, and in effect the 1.1.x version is required by all RHEL6 customers who
will be using IBM Director.
IBM is signed up to test and provide feedback.
OK, I will add it.
Bill, please add to comps when you get a chance.
Added to comps.
Planned for release in snapshot 6
------- Comment From email@example.com 2010-06-09 11:12 EDT-------
Looks good in snapshot 6
[root@ibm-x3950m2-02 6]# pwd
[root@ibm-x3950m2-02 6]# find -name "servicelog*"
See also comment #11. Moving to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.