Re: inetd servers went wrong after upgrading cygwin

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

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/

Re: inetd servers went wrong after upgrading cygwin

[Christopher Faylor]

On Tue, Jul 09, 2002 at 09:48:29AM +0800, Wu Yongwei wrote:
>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.

Ok.  That was easy.

Plonk!

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/

Re: inetd servers went wrong after upgrading cygwin

[John Vincent]

Hi,

Since you've had so much trouble trying to upgrade
your cygwin installation, can I suggest a couple of
points:

1. Make sure **NO** cygwin processes are running when
you try to install. You must stop inetd and cron, close
any bash or rxvt sessions, etc. Otherwise the installation
process may not update the DLL when you think it has.

2. Make sure you don't have more than one version of
cygwin1.dll installed. Some windows packages install
a version of the DLL without telling you, so search
your whole hard disk for any other copies, delete
any you find.

I hope these suggestions are useful.

/John Vincent.


>From: "Wu Yongwei" <adah@netstd.com>
>To: <cygwin@cygwin.com>,"John Vincent" <jpv50@hotmail.com>
>Subject: Re: inetd servers went wrong after upgrading cygwin
>Date: Sun, 7 Jul 2002 17:51:58 +0800
>
>Thank you, John. You hit on the right point!
>
>It seems setting the "HKLM\Software\Cygnus Solutions\Cygwin\Program 
>Options"
>registry key, as mentioned in /usr/doc/Cygwin/inetutils-1.3.2.README, does
>not work now. Why? If it is a change, should it be documented somewhere (an
>update of the inetutils README?)? Or is it a BUG?
>
>Thanks also go to Jim for giving me so much advice.
>
>Best regards,
>
>Wu Yongwei
>
>-- Original Message from John Vincent ---
>
>Hi,
>
>For what it's worth: when I upgraded from 1.3.9 to 1.3.10
>my inetd started behaving strangely, specifically the server
>processes were unable to start subprocesses (ftp could not ls,
>telnet could not run bash) - I'm using win2K.
>
>I found setting the CYGWIN environment variable to "ntsec"
>using the control panel fixed this. It might be worth you
>trying if you haven't already.
>
>Good Luck!
>
>John Vincent




_________________________________________________________________
Join the worldÂ’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com


--
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/

Re: inetd servers went wrong after upgrading cygwin

[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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

What is the `an "export" in the inetd list', please? More details are
appreciated.

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

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.

Best regards,

Wu Yongwei

--- Original Message from Christopher Faylor ---

I haven't actually tried this with inetd.exe.  I've just verified that
setting a key for bash.exe has the desired effect.  I also tried the
"default" option (which is basically equivalent to setting the CYGWIN
environment variable everywhere) that works fine, too.

Maybe you are suffering from the fact that you are not including an
"export" in the inetd list.  You will need that if you want the values
to propagate.  Either that or you should just use "default" rather than
"c:\\cygwin\\usr\\sbin\\inetd.exe".

>[HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
>"C:\\cygwin\\usr\\sbin\\inetd.exe"="binmode ntsec tty"
>
>defined and it used to work.

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/

Re: inetd servers went wrong after upgrading cygwin

[Don Sharp]

Wu Yongwei wrote:
> 
> So you do not define am environment variable CYGWIN, do you?
> 
> At least on this problem it seems I am not the only one affected. Mr John
> Vincent, as he said in his posting, had this problem too. My test shows
> clearly that after defining a CYGWIN environment variable with the value
> "binmode ntsec tty" and rebooting the computer the inetd works flawlessly. I
> have the registry key
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
> "C:\\cygwin\\usr\\sbin\\inetd.exe"="binmode ntsec tty"
> 
> defined and it used to work.
> 

I can confirm that you have to set the CYGWIN variable globally. It is
no longer sufficient to have the registry key to get inetd to work as it
used to under Cygwin 1.3.9.

Cheers

Don Sharp

> Some additional information in case anyone need it:
> 
> * Microsoft Windows 2000 [Version 5.00.2195]
> * Cygwin 1.3.10-1, cygwin1.dll dated 2002-02-26
> * inetutils 1.3.2-18
> 
> Since you think it should work, it seems a bug. Should I report it somewhere
> other than this list?
> 
> Best regards,
> 
> Wu Yongwei
> 
> --- Original Message from Christopher Faylor ---
> 
> On Sun, Jul 07, 2002 at 05:51:58PM +0800, Wu Yongwei wrote:
> >It seems setting the "HKLM\Software\Cygnus Solutions\Cygwin\Program
> Options"
> >registry key, as mentioned in /usr/doc/Cygwin/inetutils-1.3.2.README, does
> >not work now.
> 
> It certainly works fine for me.
> 
> >Why?
> 
> Standard response.  Everybody together now!
> 
> 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/

--
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/

Re: inetd servers went wrong after upgrading cygwin

[Christopher Faylor]

On Mon, Jul 08, 2002 at 10:03:09AM +0800, Wu Yongwei wrote:
>So you do not define am environment variable CYGWIN, do you?

No, I do not.  We were talking about the registry.

I haven't actually tried this with inetd.exe.  I've just verified that
setting a key for bash.exe has the desired effect.  I also tried the
"default" option (which is basically equivalent to setting the CYGWIN
environment variable everywhere) that works fine, too.

Maybe you are suffering from the fact that you are not including an
"export" in the inetd list.  You will need that if you want the values
to propagate.  Either that or you should just use "default" rather than
"c:\\cygwin\\usr\\sbin\\inetd.exe".

>At least on this problem it seems I am not the only one affected.  Mr
>John Vincent, as he said in his posting, had this problem too.  My test
>shows clearly that after defining a CYGWIN environment variable with
>the value "binmode ntsec tty" and rebooting the computer the inetd
>works flawlessly.  I have the registry key
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
>"C:\\cygwin\\usr\\sbin\\inetd.exe"="binmode ntsec tty"
>
>defined and it used to work.

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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

So you do not define am environment variable CYGWIN, do you?

At least on this problem it seems I am not the only one affected. Mr John
Vincent, as he said in his posting, had this problem too. My test shows
clearly that after defining a CYGWIN environment variable with the value
"binmode ntsec tty" and rebooting the computer the inetd works flawlessly. I
have the registry key

[HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
"C:\\cygwin\\usr\\sbin\\inetd.exe"="binmode ntsec tty"

defined and it used to work.

Some additional information in case anyone need it:

* Microsoft Windows 2000 [Version 5.00.2195]
* Cygwin 1.3.10-1, cygwin1.dll dated 2002-02-26
* inetutils 1.3.2-18

Since you think it should work, it seems a bug. Should I report it somewhere
other than this list?

Best regards,

Wu Yongwei

--- Original Message from Christopher Faylor ---

On Sun, Jul 07, 2002 at 05:51:58PM +0800, Wu Yongwei wrote:
>It seems setting the "HKLM\Software\Cygnus Solutions\Cygwin\Program
Options"
>registry key, as mentioned in /usr/doc/Cygwin/inetutils-1.3.2.README, does
>not work now.

It certainly works fine for me.

>Why?

Standard response.  Everybody together now!

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/

Re: inetd servers went wrong after upgrading cygwin

[Christopher Faylor]

On Sun, Jul 07, 2002 at 05:51:58PM +0800, Wu Yongwei wrote:
>It seems setting the "HKLM\Software\Cygnus Solutions\Cygwin\Program Options"
>registry key, as mentioned in /usr/doc/Cygwin/inetutils-1.3.2.README, does
>not work now.

It certainly works fine for me.

>Why?

Standard response.  Everybody together now!

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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

Thank you, John. You hit on the right point!

It seems setting the "HKLM\Software\Cygnus Solutions\Cygwin\Program Options"
registry key, as mentioned in /usr/doc/Cygwin/inetutils-1.3.2.README, does
not work now. Why? If it is a change, should it be documented somewhere (an
update of the inetutils README?)? Or is it a BUG?

Thanks also go to Jim for giving me so much advice.

Best regards,

Wu Yongwei

-- Original Message from John Vincent ---

Hi,

For what it's worth: when I upgraded from 1.3.9 to 1.3.10
my inetd started behaving strangely, specifically the server
processes were unable to start subprocesses (ftp could not ls,
telnet could not run bash) - I'm using win2K.

I found setting the CYGWIN environment variable to "ntsec"
using the control panel fixed this. It might be worth you
trying if you haven't already.

Good Luck!

John Vincent


--
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/

Re: inetd servers went wrong after upgrading cygwin

[John Vincent]

Hi,

For what it's worth: when I upgraded from 1.3.9 to 1.3.10
my inetd started behaving strangely, specifically the server
processes were unable to start subprocesses (ftp could not ls,
telnet could not run bash) - I'm using win2K.

I found setting the CYGWIN environment variable to "ntsec"
using the control panel fixed this. It might be worth you
trying if you haven't already.

Good Luck!

/John Vincent.





_________________________________________________________________
Join the worldÂ’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Jim George]

Wu Yongwei,

    another thought...someone told me that the error message you mention
below was caused by more than one cygwin1.dll on your path.  Try ensuring
that you only have the one in /bin (which has a symlink to /usr/bin).

Jim
----- Original Message -----
From: "Wu Yongwei" <adah@netstd.com>
To: <cygwin@cygwin.com>
Sent: Friday, July 05, 2002 10:00 AM
Subject: Re: inetd servers went wrong after upgrading cygwin


> Strange things happened. When I rechecked the user rights and tried to ftp
> and telnet, I found the ftp problem is gone (for both Administrator and
> anonymous user). I remember I just did a failed upgrade of cygwin and
> successful upgrades for binutils and gzip.
>
> Telnet still does not work. The same ugly 0xC0000022 application error
> appeared just when I had logged in and the message "You are successfully
> logged in to this server!!!" displayed.
>
> The home directory inherited rights from C:\, which is everyone can do
> anything, owned by Administrators (Windows default <grin>).
> /home/Administrator has the same setting. Changing it to only
Administrator
> can read and write does not solve the problem.
>
> Best regards,
>
> Wu Yongwei
>
> --- Original Message from Jim George ---
>
> Wu Yonwei,
>
> Yo mention below that everyone can write to /home, but what are the
> permissions that ftp and guest have to the directories that you are
> downloading from?
>
> Jim
>
>
> --
> 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/
>


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

Strange things happened. When I rechecked the user rights and tried to ftp
and telnet, I found the ftp problem is gone (for both Administrator and
anonymous user). I remember I just did a failed upgrade of cygwin and
successful upgrades for binutils and gzip.

Telnet still does not work. The same ugly 0xC0000022 application error
appeared just when I had logged in and the message "You are successfully
logged in to this server!!!" displayed.

The home directory inherited rights from C:\, which is everyone can do
anything, owned by Administrators (Windows default <grin>).
/home/Administrator has the same setting. Changing it to only Administrator
can read and write does not solve the problem.

Best regards,

Wu Yongwei

--- Original Message from Jim George ---

Wu Yonwei,

Yo mention below that everyone can write to /home, but what are the
permissions that ftp and guest have to the directories that you are
downloading from?

Jim


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Jim George]

Wu Yonwei,

Yo mention below that everyone can write to /home, but what are the
permissions that ftp and guest have to the directories that you are
downloading from?

Jim
----- Original Message -----
From: "Wu Yongwei" <adah@netstd.com>
To: <cygwin@cygwin.com>
Sent: Friday, July 05, 2002 3:12 AM
Subject: Re: inetd servers went wrong after upgrading cygwin


> Um, there is no second ftp entry (see below). Line split by the mailer, I
> suppose.
>
> By the way, I can log into the ftp (anonymous) account and download a
file.
> But I cannot ls. In the anonymous account, ls shows nothing. In the
> Administrator account, ls will bring up a failure message box on the
server
> machine.
>
> Best regards,
>
> Wu Yongwei
>
> --- Original Message from Jim.George ---
>
> Sorry Wu that told me didn't it :(?
>
> Anyway out of ignorance...what is the second ftp entry about?  Shouldn't
> this be on the same line, or is this the mail client causing the problem?
>
> Jim
>
> ----- Original Message -----
> From: "Wu Yongwei" <adah@netstd.com>
> To: <cygwin@cygwin.com>
> Sent: Thursday, July 04, 2002 4:17 AM
> Subject: Re: inetd servers went wrong after upgrading cygwin
>
>
> > Sorry, Jim. I replied to you because you mailed me your last message
> > personally instead of to the list.
> >
> > Everyone can write to /home. 546 is the Guests group.
> >
> > Best regards,
> >
> > Wu Yongwei
> >
> ...
>
> Everyone:*:0:0:,S-1-1-0::
> SYSTEM:*:18:18:,S-1-5-18::
> Administrators:*:544:544:,S-1-5-32-544::
>
Administrator::500:544:U-WYW\Administrator,S-1-5-21-776561741-1383384898-170
> 8537768-500:/home/Administrator:/bin/bash
>
ftp::501:546:U-WYW\Guest,S-1-5-21-776561741-1383384898-1708537768-501:/home/
> ftp:/bin/false
>
>
> --
> 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/
>


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

Um, there is no second ftp entry (see below). Line split by the mailer, I
suppose.

By the way, I can log into the ftp (anonymous) account and download a file.
But I cannot ls. In the anonymous account, ls shows nothing. In the
Administrator account, ls will bring up a failure message box on the server
machine.

Best regards,

Wu Yongwei

--- Original Message from Jim.George ---

Sorry Wu that told me didn't it :(?

Anyway out of ignorance...what is the second ftp entry about?  Shouldn't
this be on the same line, or is this the mail client causing the problem?

Jim

----- Original Message -----
From: "Wu Yongwei" <adah@netstd.com>
To: <cygwin@cygwin.com>
Sent: Thursday, July 04, 2002 4:17 AM
Subject: Re: inetd servers went wrong after upgrading cygwin


> Sorry, Jim. I replied to you because you mailed me your last message
> personally instead of to the list.
>
> Everyone can write to /home. 546 is the Guests group.
>
> Best regards,
>
> Wu Yongwei
>
...

Everyone:*:0:0:,S-1-1-0::
SYSTEM:*:18:18:,S-1-5-18::
Administrators:*:544:544:,S-1-5-32-544::
Administrator::500:544:U-WYW\Administrator,S-1-5-21-776561741-1383384898-170
8537768-500:/home/Administrator:/bin/bash
ftp::501:546:U-WYW\Guest,S-1-5-21-776561741-1383384898-1708537768-501:/home/
ftp:/bin/false


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Jim George]

Sorry Wu that told me didn't it :(?

Anyway out of ignorance...what is the second ftp entry about?  Shouldn't
this be on the same line, or is this the mail client causing the problem?

Jim

----- Original Message -----
From: "Wu Yongwei" <adah@netstd.com>
To: <cygwin@cygwin.com>
Sent: Thursday, July 04, 2002 4:17 AM
Subject: Re: inetd servers went wrong after upgrading cygwin


> Sorry, Jim. I replied to you because you mailed me your last message
> personally instead of to the list.
>
> Everyone can write to /home. 546 is the Guests group.
>
> Best regards,
>
> Wu Yongwei
>
> --- Original Message from Jim.George ---
>
> On Tue, 2 Jul 2002, Wu Yongwei wrote:
>
> > Thank you, but it will not do. The users used to be in the None group
and
> > inetd worked; they are now in the relevant groups (Administrators or
> Guests)
> > but inetd still does not work.
> >
> > Can you find problems in such a passwd file?
> >
> > ---
> > Everyone:*:0:0:,S-1-1-0::
> > SYSTEM:*:18:18:,S-1-5-18::
> > Administrators:*:544:544:,S-1-5-32-544::
> >
>
Administrator::500:544:U-WYW\Administrator,S-1-5-21-776561741-1383384898-170
> > 8537768-500:/home/Administrator:/bin/bash
> >
>
ftp::501:546:U-WYW\Guest,S-1-5-21-776561741-1383384898-1708537768-501:/home/
> > ftp:/bin/false
> > ---
> >
> > Best regards,
> >
> > Wu Yongwei
> >
>
> Please can you keep your questions/answers on-list so that all can
> benefit?
>
> I am suspicious of the ftp user account?  What group has permissions to
> the whole of /home?
>
> Jim
>
> > --- Original Message from Jim George ---
> >
> > This has been dealt with (recently) in the archives.  It happened to me.
> I
> > think I had to remake passwd and group and ensure that my remote users
> were
> > in passwd and that they were not allocated the 'None' group.
> >
> > HTH
> >
> > Jim
>
>
> --
> 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/
>


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

Sorry, Jim. I replied to you because you mailed me your last message
personally instead of to the list.

Everyone can write to /home. 546 is the Guests group.

Best regards,

Wu Yongwei

--- Original Message from Jim.George ---

On Tue, 2 Jul 2002, Wu Yongwei wrote:

> Thank you, but it will not do. The users used to be in the None group and
> inetd worked; they are now in the relevant groups (Administrators or
Guests)
> but inetd still does not work.
>
> Can you find problems in such a passwd file?
>
> ---
> Everyone:*:0:0:,S-1-1-0::
> SYSTEM:*:18:18:,S-1-5-18::
> Administrators:*:544:544:,S-1-5-32-544::
>
Administrator::500:544:U-WYW\Administrator,S-1-5-21-776561741-1383384898-170
> 8537768-500:/home/Administrator:/bin/bash
>
ftp::501:546:U-WYW\Guest,S-1-5-21-776561741-1383384898-1708537768-501:/home/
> ftp:/bin/false
> ---
>
> Best regards,
>
> Wu Yongwei
>

Please can you keep your questions/answers on-list so that all can
benefit?

I am suspicious of the ftp user account?  What group has permissions to
the whole of /home?

Jim

> --- Original Message from Jim George ---
>
> This has been dealt with (recently) in the archives.  It happened to me.
I
> think I had to remake passwd and group and ensure that my remote users
were
> in passwd and that they were not allocated the 'None' group.
>
> HTH
>
> Jim


--
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/

Re: inetd servers went wrong after upgrading cygwin

[Jim.George]

On Tue, 2 Jul 2002, Wu Yongwei wrote:

> Thank you, but it will not do. The users used to be in the None group and
> inetd worked; they are now in the relevant groups (Administrators or Guests)
> but inetd still does not work.
>
> Can you find problems in such a passwd file?
>
> ---
> Everyone:*:0:0:,S-1-1-0::
> SYSTEM:*:18:18:,S-1-5-18::
> Administrators:*:544:544:,S-1-5-32-544::
> Administrator::500:544:U-WYW\Administrator,S-1-5-21-776561741-1383384898-170
> 8537768-500:/home/Administrator:/bin/bash
> ftp::501:546:U-WYW\Guest,S-1-5-21-776561741-1383384898-1708537768-501:/home/
> ftp:/bin/false
> ---
>
> Best regards,
>
> Wu Yongwei
>

Please can you keep your questions/answers on-list so that all can
benefit?

I am suspicious of the ftp user account?  What group has permissions to
the whole of /home?

Jim

> --- Original Message from Jim George ---
>
> This has been dealt with (recently) in the archives.  It happened to me.  I
> think I had to remake passwd and group and ensure that my remote users were
> in passwd and that they were not allocated the 'None' group.
>
> HTH
>
> Jim
> ----- Original Message -----
> From: "Wu Yongwei" <adah@netstd.com>
> To: <cygwin@cygwin.com>
> Sent: Monday, July 01, 2002 10:53 AM
> Subject: inetd servers went wrong after upgrading cygwin
>
>
> > I do not know at which point, but telnetd and ftpd do not work now; they
> > used to. The symptom is that when I log in to telnetd, the system pops up
> an
> > application initialization failure (0xc0000022); when I type ls after
> > logging in to ftpd, a similar failure appears (using Administrator) or no
> > files are listed (using anonymous).
> >
> > I tried to install the same Cygwin distribution to another computer, the
> > same thing happened. So it is not likely to be caused by some
> configuration
> > of my computer. Both computers run Windows 2000.
> >
> > Anybody experiences similar things or has a clue what happened?
> >
> > Best regards,
> >
> > Wu Yongwei
> >
>


--
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/

inetd servers went wrong after upgrading cygwin

[Wu Yongwei]

I do not know at which point, but telnetd and ftpd do not work now; they
used to. The symptom is that when I log in to telnetd, the system pops up an
application initialization failure (0xc0000022); when I type ls after
logging in to ftpd, a similar failure appears (using Administrator) or no
files are listed (using anonymous).

I tried to install the same Cygwin distribution to another computer, the
same thing happened. So it is not likely to be caused by some configuration
of my computer. Both computers run Windows 2000.

Anybody experiences similar things or has a clue what happened?

Best regards,

Wu Yongwei


--
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/