From: Paul Jackson <pj@engr.sgi.com>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH][RFC] Apply umask to /proc/<pid>
Date: Sat, 12 Mar 2005 21:10:59 -0800 [thread overview]
Message-ID: <20050312211059.6ad4e08b.pj@engr.sgi.com> (raw)
In-Reply-To: <20050312211255.GA4627@lsrfire.ath.cx>
> patch below makes procfs apply the umask of the processes to their
> respective /proc/<pid> directories and the files below them.
Ugh ...
Since there are already various umask settings done by various
/etc/*profile* and /etc/*init* scripts that head up various logins and
task families, this means that the default visibility of tasks in ps and
top will change. I predict confusion and frustration, when people don't
know why portions of ps or top output are suppressed.
And even when they figure it out, you don't give them anyway to get back
to the previous state - of visibility in ps, top and pstree, but file
creation permissions masked off in some way.
Nice small patch ... but I don't like overloading umask with this.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-03-13 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 21:12 [PATCH][RFC] Apply umask to /proc/<pid> Rene Scharfe
2005-03-13 5:10 ` Paul Jackson [this message]
[not found] <fa.ft6scin.15lkbgv@ifi.uio.no>
2005-03-13 1:23 ` Bodo Eggert
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=20050312211059.6ad4e08b.pj@engr.sgi.com \
--to=pj@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox