Bug 86304
| Summary: | loadavg ability(max_load attribute) is not supported | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | SEKINE Tatsuo <sekine.t> |
| Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
| Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | jfeeney |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-13 17:14:02 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: | |||
I change status from RFE to BUG. Because the man page of xinetd.conf refers the "max_load" capability without (configure-)limitation, but RedHat's xinetd doesn't support it. An errata 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-2003-160.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.1) Gecko/20021030 for VineLinux 0vl6 Description of problem: Xinetd equip load average-based resource limitation functionality. But it is disabled by default. Please add --with-loadavg configure option to the spec. Version-Release number of selected component (if applicable): xinetd-2.3.10-4 How reproducible: Always Steps to Reproduce: 1. /usr/sbin/xinetd -version 2. 3. Actual Results: xinetd Version 2.3.10 libwrap Expected Results: xinetd Version 2.3.10 libwrap loadavg Additional info: Disabling the functionality in configuration file is easy. If you don't specify "max_load" attribute, the functionality is disabled. Therefore, in the view of compatibility, enabling the functionality is no problem.