On Apr 21 02:17, Brian Dessent wrote: > Brian Dessent wrote: > > > Right, I wasn't trying to imply that the location of the shared section > > had anything to do with IL, just explaining why his elevated shell in > > session 1 could see the processes of services in session 0 (i.e. because > > the elevated session 1 could create the shared section in the global > > namespace and read the cygwin process table.) > > Oh wait, I think I see what you're saying: that regardless of IL, the > output of 'ps' depends solely on the Cygwin shared process table and not > being able to open a process object.
Yep. The problem is that there isn't one process table, but one process table per session. > But then, ps -W would depend on IL, since that includes non-Cygwin > processes that aren't included in the Cygwin pid table, right? Not IL, afaik. It's all about session isolation. Non-privileged users can't see processes outside of their session. That's also already the case since at least Windows 2K3. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
