Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <000701c226ea$ba5d88d0$0610a8c0@wyw>
From: "Wu Yongwei" <adah AT netstd DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Re: inetd servers went wrong after upgrading cygwin
Date: Tue, 9 Jul 2002 09:48:29 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I tried "export". The result is a terrible failure:

$ telnet localhost
Trying 127.0.0.1...
Connected to wyw.
Escape character is '^]'.
Connection closed by foreign host.

Without "export" I can go a little further:

$ telnet localhost
Trying 127.0.0.1...
Connected to wyw.
Escape character is '^]'.

CYGWIN_NT-5.0 1.3.10(0.51/3/2) (wyw) (tty0)

login: Administrator
Password:
Last login: Tue Jul  9 09:39:41 from wyw
Fanfare!!!
You are successfully logged in to this server!!!
Connection closed by foreign host.

I will not try "default". The point that I want to use the registry entry is
that I do not want a global ntsec setting.

You are really helping, but I am not harming, either. I am in some aspects
your beta user. I already know one way how to make inetd work, but I am now
testing Cygwin trying bitterly to find out the reasons of the problems.

Whatever it is, the file /usr/doc/Cygwin/inetutils-1.3.2.README needs an
update. One way it mentions no longer works. I confirmed this browsing the
Cygwin message archive of February.

Best regards,

Wu Yongwei

--- Original Message from Christopher Faylor ---

On Mon, Jul 08, 2002 at 04:35:57PM +0800, Wu Yongwei wrote:
>What is the `an "export" in the inetd list', please? More details are
>appreciated.

Add the word "export" to the registry entry.

http://cygwin.com/cygwin-ug-net/using-cygwinenv.html

>BTW, I also tried setting a value under "...\Cygwin\Program Options" for
>"c:\\cygwin\\usr\\sbin\\in.telnetd.exe", with no luck.

Did you try using "default" as I suggested?  What I mean is that you
should replace "c:\\cygwin\\usr\\sbin\\in.telnetd.exe" with "default".

This will cause the settings to be the default for all cygwin programs.

>And I tried downgrading to Cygwin 1.3.9-1 and confirmed that without a
>global environment variable CYGWIN inetd ran flawlessly under Cygwin
>1.3.9-1.  So it must be caused by some changes from Cygwin 1.3.9-1 to
>1.3.10-1, as mentioned by Mr John Vincent.  Sorry I cannot test with
>newer Cygwin releases since they simply won't run, which is caused by
>some other changes unknown to me.

If you want to go to the effort of tracking down the change in the code
where something changed, then that would be useful.  Otherwise, I doubt
that anyone is going to smack their head and say "Aha! 1.3.9 to 1.3.10!
Of course!" 1.3.10 was released in February.  1.3.9 was released in
January.  My memory of specific changes does not extend back that far.

I suspect that either adding "export" to the list of options to the
inetd registry key or using "default" will solve your problem but you
seem insistent on extending this dance.  I'm trying to help but if you
don't want to try the things that I'm suggesting then I will just stop
suggesting.

cgf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/