Bug 248157
Summary: | qdisk integration with watchdog daemon | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Lon Hohberger <lhh> |
Component: | cman | Assignee: | Marek Grac <mgrac> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | cluster-maint, krzeszut |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-09-04 11:15:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lon Hohberger
2007-07-13 14:56:25 UTC
This will require changes to the watchdog daemon. Generally, what I'm after here is a way for other apps to read from the watchdog daemon's internal state. This functionality may already exist, however, the specifics are that it should be a low-overhead method - like shared memory or something - so that we can be as memory-neutral as possible (compared to a socket which allocates buffers, for example). Moving this to 5.3 unless Marek has something ready. This could be stabilizing to the watchdog daemon. Er, destabilizing... |