From:	huott AT pinebush DOT com (Ed Huott)
Subject:	Re: cygwin.dll problem with multiple users
18 Mar 1997 22:48:48 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199703182217.RAA16354.cygnus.gnu-win32@sol.pinebush.com>
Original-To:	Shankar Ramamoorthy <shankar AT viman DOT com>
Original-Cc:	gnu-win32 AT cygnus DOT com
In-reply-to:	Your message of "Mon, 17 Mar 1997 20:24:32 PST."
	<332E1900 DOT 4A8B AT viman DOT com>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

In message <332E1900 DOT 4A8B AT viman DOT com>, Shankar Ramamoorthy writes:
>[I've looked in the FAQ and mail archives for a mention of this
> but did not see anything. If it is there, just point me at it.
>]
>
>What follows is w.r.t Windows NT 4.0 and Cygwin Beta 17.1.
>
>Can two different users simultaneously use programs linked against
>cygwin.dll? It doesn't seem to work for me.
>
>For example: I log is as administrator and start bash.
>Then telnet in as another user. When I try to start bash within the
>telnet session I get:
>  (unknown) shared_init:
>CreateFileMappingA                                       
>  cygwin: terminating
>Now I exit the bash session started as administrator. I am now
>able to start bash in the telnet session.
>

I can confirm that this identical problem also exists using NT 3.51
and Cygwin Beta 17.1.  I don't recall seeing it in the FAQ either.
It's possible it's been posted to this list before (though I've been
following along for several months and don't recall it, specifically.)

It seems as though once the cygwin.dll is loaded by a particular
client process, any other client process running in a different
security context will drive this bug when it goes to initialize.

<ED>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -