From: wrw AT decisionism DOT com (Randy Watler)
Subject: Question: concurrent users using gnu-win32 tools/shared_init?
6 Sep 1997 15:06:49 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199709042157.PAA14911.cygnus.gnu-win32@plover.decisionism.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Original-To: GNU-Win32 AT cygnus DOT com
Content-MD5: Ppb+y7ZMbZk3YXGLFshuZg==
Original-Sender: owner-gnu-win32 AT cygnus DOT com

We are currently using the gnu-win32 tools, (b17.1), to perform builds
on a multi-processor NT server. When multiple users are logged into
the machine via telnetd, (from Ataman TCP), and attempt to use most any
of the cygwin tools simultaneously, they crash with the following message
to the telnet session:

(unknown) shared_init:CreateFileMappingA
cygwin:terminating

and with a generic "cannot read from address" terminal dialog.

Looking at the source, we believe that these messages originate from
winsup/shared.cc. It apparently tries to allocate shared memory with
a security descriptor that allows 'all' access. Somehow this is failing
when concurrent users perform this function?

Is there some setup that we have blown or is this a known limitation?

Thanks,

Randy Watler
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".