> For all of these, I think the right thing is to extend the proc
> server. The point of proc_getprocinfo is to provide "whatever ps
> needs".
Ok. I'm not going to worry about ids for the moment.
For libps the most obvious thing is to add task_events_info to procinfo.
I'll do that. In fact,
--- "Thomas Bushnell, BSG" <[EMAIL PROTECTED]> wrote:
> Roland McGrath <[EMAIL PROTECTED]> writes:
>
> > ids -- Does pid2task to query arbitrary processes auth ports.
> >Seems like a questionable need. If that info should be public,
> >we could just have the proc server publish
Roland McGrath <[EMAIL PROTECTED]> writes:
> ids -- Does pid2task to query arbitrary processes auth ports.
> Seems like a questionable need. If that info should be public,
> we could just have the proc server publish the id lists it got
> in its auth transactions (wh
They are:
login -- Falls back to unix-style if password server is not there.
If we can presume the password server works, then we can
clear the setuid bit here. (We could also remove the old code,
or leave it there for only root to be able to use w/o server.)
i
