Red Hat Bugzilla – Bug 633355
[6.1 FEAT] Enhance cio_ignore usage in scripts using new handler for pending work - post.config tools part
Last modified: 2010-11-30 05:11:49 EST
1. Feature Overview:
Feature Id: 
a. Name of Feature: [6.1 FEAT] Enhance cio_ignore usage in scripts using new handler for pending
work - post.config tools part
b. Feature Description
This feature requests to enhance the cio_ignore usage in post-configuration tools by taking
advanctage of the new cio_ignore handler to wait for cio pending work.
2. Feature Details:
Sponsor: LTC zSeries BOE
zSeries - 64 native,
Arch Specificity: purely arch specific code
Affects Kernel Modules: Field does not exist
Delivery Mechanism: LDP Deliverable
Request Type: Code Development Support from Distributor
d. Upstream Acceptance: Field does not exist
Sponsor Priority P1
f. Severity: ship issue
IBM Confidential: No
Code Contribution: 3rd party code
g. Component Version Target:
3. Business Case
This feature will avoid running into possible race condition, making the code more stable.
Resulting on less service cost and better customer satisfaction.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, email@example.com
Gonzalo Muelas Serrano, firstname.lastname@example.org
------- Comment From email@example.com 2010-10-04 10:42 EDT-------
Code Upstream Status: No Code Required
IBM, can you please provide more details on what is being requested here?
This doesn't seem to relate to system-config-services, closing.
------- Comment From firstname.lastname@example.org 2010-11-30 05:02 EDT-------
Close this feature request as duplicate
to 66875 - RHBZ 631527 - [6.1 FEAT] Provide userspace handle to wait for cio
pending work - userspace
The functionality could be implemented into s390tools (s390utils) only and get referred to during install and boot.
The calls from installer and scripts already exist with RHEL6 (6.0 FEAT cio_ignore...) feature request.
So nothing to implement for post config tools anymore.
*** This bug has been marked as a duplicate of bug 66875 ***