Re: procfs: boot- and runtime configurable access mode for/proc/<pid> dirs

[Alexey Dobriyan]

On Thu, Mar 24, 2011 at 09:41:58AM +0100, Daniel Reichelt wrote:
> > Keeping u/g/o inside kernel is horrible.
> 
> Why exactly? Since it's only a char and not char[] I don't see the
> disadvantage over int or a define or whatever. Of course I could always
> change that if that's a de-facto standard I just didn't know about.

Keep mode_t inside kernel, this will get rid of many ifdefs.
 
> > What is the usecase? Content of /proc/* is identical.
> 
> Use-case is to isolate process information from other users' or groups'
> eyes, e.g. with 550 the output of ps aux only lists processes of the
> groups your user is a member of.

This is doable with some ps(1) switch, I'm sure.

The content of /proc/$PID directory is not a secret.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/