Bug 156882 - aggressively clean bhs
aggressively clean bhs
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Larry Woodman
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-04 17:24 EDT by Van Okamura
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-04 21:32:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to aggressively clean bhs (390 bytes, patch)
2005-05-04 17:24 EDT, Van Okamura
no flags Details | Diff

  None (edit)
Description Van Okamura 2005-05-04 17:24:16 EDT
Description of problem:
Need to more aggressively clean bhs to avoid running out of memory.

Version-Release number of selected component (if applicable):
2.4.21-27.0.2

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
The attached patch gets around this.
Comment 1 Van Okamura 2005-05-04 17:24:16 EDT
Created attachment 114043 [details]
patch to aggressively clean bhs
Comment 2 Van Okamura 2005-05-04 17:25:18 EDT
The solution in bugzilla 144871 should get around this on
Comment 3 Ernie Petrides 2005-05-04 21:32:39 EDT

*** This bug has been marked as a duplicate of 144871 ***
Comment 4 Tim Powers 2005-05-18 09:29:27 EDT
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.

http://rhn.redhat.com/errata/RHSA-2005-294.html

Note You need to log in before you can comment on or make changes to this bug.