Bug 8277
Summary: | Red Hat Linux 6.0 consumes free memory too fast | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | strokop |
Component: | apache | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http:/www.aecom.yu.edu/xray | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-01-13 02:34:49 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
strokop
2000-01-07 20:44:25 UTC
The free command only displays the total system usage. Try using ps and/or top to identify what process is using memory. If the process is the apache server, you might want to restart the process daily/weekly in order to free the memory. There's also a known memory leak in gethosbyname when running nscd in Red Hat 6.0. Either upgrade glibc to the latest 6.0 errata, or don't start nscd. As jeff said, Linux has an efficient file and program cache. When 'free' approaches zero, you really aren't at zero. If a new program needs memory, it will be allocated from the cache. Not a bug, trust us. |