Re: About "messed up user permissions from w2k terminal session"

["Pierre A. Humblet" <Pierre dot Humblet at ieee dot org>]

Corinna Vinschen wrote:
> 
> On Mon, Oct 06, 2003 at 07:28:57PM -0400, Pierre A. Humblet wrote:
> >
> > I don't know what to think of the problem reported in
> > http://cygwin.com/ml/cygwin/2003-10/msg00302.html
> >
<snip>
> 
> A named file sharing created with open_shared() is always created
> in the Global\ namespace, see shared_name().  Unfortnately I'm under
> the impression that mystifies the failing CreateFileMapping instead
> of clearing anything up.

You are right, and that was done in May 2003. But that raises the issue
of whether the problem occurs because of my change in 1.5.4 or whether
it was there since 1.5.1

> > On the other hand, the name space explains the following:
> > >>1) When you run 1.3.22 and you do ps -a from a Terminal Server session,
> > do you
> > >>see all Cygwin processes on the machine or only yours?
> >
> > >Only mine, only the ones that I have launched from my window/login session.
> >
> > Do we want it this way or should the pinfos (and all other Cygwin shared)
> > use the global name space?
> 
> IMHO the pinfo object should be in the Global\ namespace to allow a UNIX
> like process list with all running processes.  Isn't that also necessary
> to be able to send signals to your own processes which are just happen to
> run in another terminal session?  You can't do this if the pinfo is in
> a disjunctive namespace, or is that not the case?

You are right, you won't see your own processes in other sessions and you 
won't find their signal pipes.

There is this sentence in the MS page I cited yesterday:
"Starting with Windows?Server 2003, the creation of a global section from a
session other than the initial system session (where clients run) is a
privileged operation. Because of this, an application running in an 
arbitrary Terminal Server session must have SeCreateGlobalPrivilege enabled
in order to create a global section successfully. "

Is that privilege given routinely by MS? If not, having global objects will
create problems as 2003 spreads. Fortunately we now have editrights (which
crashes on my Nt4.0, but that's another story)....

I will check if this privilege might be related to the reported problem.

Pierre