[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CA0465F.6080508@redhat.com>
Date: Mon, 27 Sep 2010 15:23:11 +0800
From: Eugene Teo <eugene@...hat.com>
To: Neil Horman <nhorman@...driver.com>
CC: Jiri Olsa <jolsa@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, oleg@...sign.ru
Subject: Re: [RFC PATCH] proc: making "limits" world readable
On 09/25/2010 12:20 AM, Neil Horman wrote:
> On Fri, Sep 24, 2010 at 12:55:47PM +0200, Jiri Olsa wrote:
>> On Thu, Sep 23, 2010 at 02:56:42PM -0700, Andrew Morton wrote:
>>> On Tue, 21 Sep 2010 11:10:55 +0200
>>> Jiri Olsa<jolsa@...hat.com> wrote:
>>>
>>>> hi,
>>>>
>>>> I'd like to have the /proc/<pid>/limits file world readable,
>>>
>>> Why?
>>>
>>
>> having this will ease the task of system management for large install
>> bases and where root privileges might be restricted
>>
>> jirka
>>
> I don't see a problem with making this file world readable. Doing so would be
> in keeping with most of the other stats bearing files in /proc/<pid>. The only
> reason I didn't make it world readable was because the getrlimit sematics
> previously kept limit information private to the process, and I didn't want to
> deviate from that. But as long as we're not making it world writeable I think
> we're ok.
>
> Acked-by: Neil Horman<nhorman@...driver.com>
I agree with Neil. I can't see how this can be a problem as long as it
is just world-readable.
Eugene
--
main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i); }
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists