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: <37AA044E.C6095286@vinschen.de>
Date: Thu, 05 Aug 1999 23:38:22 +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: Chris Faylor <cgf AT cygnus DOT com>
CC: cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>,
        "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: ntsec: patch 9
References: <37A8114F DOT 9101F2AE AT vinschen DOT de> <19990804214745 DOT A15316 AT cygnus DOT com> <37A9682E DOT EA185B11 AT vinschen DOT de> <19990805113216 DOT A973 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

Chris Faylor wrote:
> 
> I am not seeing anything like this.  I've just done a couple of configure/make
> cycles with no problems.
> 
> Do you have anything special in your CYGWIN environment variable?

inetd and it's subprocesses are started with:

	CYGWIN=binmode tty ntea ntsec

bash or tcsh from cmd window are started with:

	CYGWIN=binmode notty ntea ntsec

or for testing purposes with:

	CYGWIN=binmode notty ntea nontsec

> On reviewing the changes between 17-Jul and 26-Jul, the only thing that I see
> that could affect anything is changes I made to detect multiple cygwin DLLs
> being used.
> 
> You don't, by any chance, have more than one DLL in your path or on your system
> do you?

The answer is definitely 'no'. In my environments on every computer cygwin1.dll
is in /usr/bin directory. If I test new dlls, I rename the old one to e.g
cygwin1.dllX and copy the new one again to /usr/bin. With this method, I don't
have evil surprises. Moreover I have explicitly checked it by running `find'.

I know, it's not the answer, you like to get :-(

Should we (Larry and me) try it without the aforementioned detection code?
If so, how can I disable it?

Regards,
Corinna