Red Hat Bugzilla – Bug 132257
LTC-8859: softdog.o need to be included into RHEL distributions
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
softdog.o is required for "dead man switch" functionality. This
allows for the following: unless the application "contacts" the
module periodically, the kernel reboots. This is used in our High-
Availability software to ensure that critical software components of
the system are not blocked for long periods. If they do get blocked
then the OS needs to crash.
System Automation can not support RHEL without softdog. As of
bugzilla LTC-8859 it was requested for RHEL 3 U3. We verified U3, but
softdog is not included. This problem need to be fixed with RHEL 3 U4
latest. Problem is also applicable for RHEL 4.
I opened an LDP requirement too (LDP req. 91042).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.use softdog functionality
This is a feature request, not a bug report.
You know the process here - this goes thru Issue tracker, not buzilla.
We did this for PPC for U2, why now for mainframe ?
Sorry, Bob. I wasn't sure, if this is a feature request, because
there is an open LTC bugzilla. Our System Automation product requires
that support. Without it, RHEL 3 can not be supported. Tivoli System
Automation for Linux is one of the key Linux system management
products for complex applications/middleware.
Should I open an issue tracker ?
Yes this should be a feature request, LDP and IT.
The s390,x software watchdog support was committed to the RHEL3 U5
patch pool on 18-Feb-2005 (in kernel version 2.4.21-27.16.EL).
The s390,x software watchdog config changes have just been committed to
the RHEL3 U5 patch pool this evening (in kernel version 2.4.21-32.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.