From: Chris Wright <chrisw@osdl.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: sds@epoch.ncsc.mil, Andrew Morton OSDL <akpm@osdl.org>,
serue@us.ibm.com,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] audit: handle loginuid through proc
Date: Thu, 24 Feb 2005 22:49:09 -0800 [thread overview]
Message-ID: <20050225064909.GD28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1109312092.5125.187.camel@cube>
* Albert Cahalan (albert@users.sourceforge.net) wrote:
> Assuming you'd like ps to print the LUID, how about
> putting it with all the others? There are "Uid:"
> lines in the /proc/*/status files.
It's also set (written) via /proc, so it should probably stay separate.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-02-25 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 6:14 [PATCH] audit: handle loginuid through proc Albert Cahalan
2005-02-25 6:49 ` Chris Wright [this message]
2005-02-25 15:15 ` Albert Cahalan
2005-02-25 17:08 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2005-01-27 17:36 [PATCH] [audit] " Serge E. Hallyn
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=20050225064909.GD28536@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.com \
/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.