Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <37AC22DF.643FC4E3@vinschen.de>
Date: Sat, 07 Aug 1999 14:13:20 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: earnie_boyd AT yahoo DOT com
CC: cygwin developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: 19990805 Snapshot!!
References: <19990806232455 DOT 20042 DOT rocketmail AT web129 DOT yahoomail DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Earnie Boyd wrote:
> Corinna, if you have Win9x and you also have created an /etc/passwd and
> /etc/group files will the ntsec code cause problems?

The code can't conflict with 9X because 9X doesn't have any security.
Moreover, ntsec is in general off on 9X systems.

> Further notes on the ntsec problem, in starting a second bash, I'm no longer
> the owner of the child process ( or so it appears ).  I can't kill it with the
> [...]

The described problem is not related to ntsec. I can reproduce it, too,
regardless of the setting of ntsec.

> NT4 sp3 Normal domain user.  I have no /etc/passwd and no /etc/group files.
> CYGWIN=notty binmode notitle.

As I mentioned often enough before: ntsec is really dependent on correct
installed /etc/passwd and /etc/group files. If you don't have it, create it.
Read winsup/doc/ntsec.sgml for more info.

Please, send the strace to Chris, too. Maybe, he finds sth.

I have made a tiny patch to ntsec which is related to the get_signal_mutex
problem, maybe, but since I can't reproduce your problem, I don't know.
I have send it to Chris and the mailing list as ntsec patch 10. Please,
try it, as far as it is published.

Regards,
Corinna