Bug 468380
Summary: | backport /proc/<pid>/limits feature | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Helge Deller <helge.deller> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Jenner <mjenner> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.4 | CC: | hannes.kuehnemund, jpirko, linux, rdoty |
Target Milestone: | rc | Keywords: | FutureFeature, OtherQA |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-29 07:21: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: | |||
Bug Depends On: | |||
Bug Blocks: | 460679, 468381 |
Description
Helge Deller
2008-10-24 13:54:33 UTC
Helge, what do you exactly need to be backported? As I tested it with 2.6.18-92.el5 I can see resource limits via "cat /proc/<pid>/limits" (unlike rhel4). Thanks. please take a look at bug 253762, kernel version 2.6.18-60.el5+ in 5.2 GA. Because this feature has already been backported to 253762. Please let us know if 5.2's implementation does not meet your needs. thanks. Sorry, the short description of bug 461946 was not complete. It should also state, that it should be possible to change the limits during runtime. As an example, "Core file size" is usually set to "0" (no core is written), but you for debugging purposes you have to change this for a certain binary to write a core file w/o restarting it. Therefore, it should also be possible to change the limits of a process during runtime. Ok, misunderstanding from our side. Showing limits is fine in the first place. You can close this BZ, thx Ok. Thanks Hannes. Closing the bug. Closed as "currentrelease", instead of "not a bug", since it was already backported into RHEL 5.2 and it was not in RHEL 5.0. |