From: Pavel Machek <pavel@ucw.cz>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] /proc/<pid>/rlimit
Date: Thu, 20 Jan 2005 15:43:58 +0100 [thread overview]
Message-ID: <20050120144358.GI476@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050118204457.GA7824@ti64.telemetry-investments.com>
Hi!
> This patch against 2.6.11-rc1-bk6 adds /proc/<pid>/rlimit to export
> per-process resource limit settings. It was written to help analyze
> daemon core dump size settings, but may be more generally useful.
> Tested on 2.6.10. Sample output:
>
> root@tiny ~ # cat /proc/__/rlimit
> cpu unlimited unlimited
> fsize unlimited unlimited
> data unlimited unlimited
> stack 8388608 unlimited
> core 0 unlimited
> rss unlimited unlimited
> nproc 111 111
> nofile 1024 1024
> memlock 32768 32768
> as unlimited unlimited
> locks unlimited unlimited
> sigpending 1024 1024
> msgqueue 819200 819200
>
> Feedback welcome.
It would be nice if you could make it "value-per-file". That way,
it could become writable in future. If "max nice level" ever becomes rlimit,
this would be very usefull.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-01-20 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 20:44 [RFC][PATCH] /proc/<pid>/rlimit Bill Rugolsky Jr.
2005-01-19 7:11 ` Chris Wright
2005-01-19 19:31 ` Jan Knutar
2005-01-19 19:38 ` Chris Wright
2005-01-19 20:13 ` Bill Rugolsky Jr.
2005-01-19 20:47 ` Chris Wright
2005-01-20 14:43 ` Pavel Machek [this message]
2005-01-21 2:19 ` Bill Rugolsky Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050120144358.GI476@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=brugolsky@telemetry-investments.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.