This is the mail archive of the cygwin-developers@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ntsec: patch 9


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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]