* Albert Cahalan ([EMAIL PROTECTED]) wrote:
> On Thu, 2005-02-24 at 22:49 -0800, Chris Wright wrote:
> > * Albert Cahalan ([EMAIL PROTECTED]) 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
On Thu, 2005-02-24 at 22:49 -0800, Chris Wright wrote:
> * Albert Cahalan ([EMAIL PROTECTED]) 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 sho
* Albert Cahalan ([EMAIL PROTECTED]) 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 Modul
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kerne
The audit subsystem uses netlink messages to request loginuid
changes. Due to the sensitivity of loginuid, netlink appears to
be insufficient. For instance, it is not easy to guarantee that
the loginuid message will be handled before any other auditable
actions, and there is even the remote possi
5 matches
Mail list logo