Messages in this thread | | | Subject | Re: [PATCH]: proc: export a processes resource limits via proc/<pid> | From | Valdis.Kletnieks@vt ... | Date | Fri, 17 Aug 2007 16:20:45 -0400 |
| |
On Fri, 17 Aug 2007 12:45:47 PDT, Andrew Morton said: > On Fri, 17 Aug 2007 06:59:18 -0400 > Neil Horman <nhorman@tuxdriver.com> wrote: > > > Currently, there exists no method for a process to query the resource > > limits of another process. They can be inferred via some mechanisms but they > > cannot be explicitly determined. Given that this information can be usefull to > > know during the debugging of an application, I've written this patch which > > exports all of a processes limits via /proc/<pid>/limits. > > I'm struggling with this a bit. Sure, it _might_ be handy on some > occasions to be able to get at this information. But I've never seen > anyone ask for it before, and it _is_ determinable by other means, if only > strace.
Most of the times *I*'ve struggled with this, it's been a case of "this program forks that one that calls a PAM module that does this and then double-forks yadda yadda". So I know where Neil is coming from.
> How do we justify adding yet more stuff to the kernel?
I looked the code over, and *if* we want to do it, the code looks good. Making that final call is why they pay you and Linus the big bucks. :)
[unhandled content-type:application/pgp-signature] | |