Inetd 1.3.2-14 problems

[Bruce Dobrin]

Corinna,

I got it working,  but I'm not sure exactly how, and the solution has caused
a different (but much less severe) problem.  Here's a rundown on what I
did.. maybe it'll help someone you figure it out,  or someone else who might
be having the problem

First I backed up the cygwin and blew it away, then removed it from the
registry and re-installed from the web.

still didn't work.

I removed my copy of the cygwin1.dll from the system32 directory and made
sure the path was correct (c:/cygwin/usr/bin),  then I couldn't even get the
service to start correctly consistently (which is why I have a script to put
the correct one there to begin with).  Put the cygwin1.dll back,  now the
service starts and stops correctly,  but I still can't get past the
password.
Then I removed the registry addition of the C:\cygwin\usr\sbin\inetd.exe
<etc> suggested in the "inet.....README" file.   still didn't work,
then I put set the global CYGWIN env variable to my old settings..  Nothing.
then I reset the CYGWIN env variable to  CYGWIN = "binmode tty ntsec" ......
still nothing
then I rebooted 2 times.  And it started to work.
I think it was the "binmode tty ntsec"  that did it,  but I'm not sure.
Also why the alternate method didn't work.

But Now I can't compile  unless I unset the CYGWIN variable (as per mailing
list message from Reid Thompson Date: Fri, 30 Mar 2001 07:41:46 -0500).

Do you have any Idea why it wouldn't work with the reg setting?  and is
there a solution to the GCC/ntsec problem?.

Thanks
Bruce
----- Original Message -----
From: "Bruce Dobrin" <dobrin@imageworks.com>
To: <cygwin@cygwin.com>
Sent: Wednesday, June 13, 2001 11:26 AM
Subject: Re: Inetd 1.3.2-14 problems


> Yes, it is 18  :
> dobrin@GUS:/home/dobrin> ps -e
>       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>       299       1     299        299    ?   18 15:57:48 /usr/sbin/inetd
>       311     299     299        311    ?   18 15:57:48 /usr/sbin/inetd
>       219       1     219        219  con 11014 09:32:31 /usr/bin/bash
>       376     219     376        322  con 11014 09:32:31 /usr/bin/tcsh
>       380     311     299        386    ?   18 09:38:04
/usr/sbin/in.rlogind
>       436     380     436        373    0   18 09:38:05 /usr/bin/login
>       445     376     445        248  con 11014 09:38:08 /usr/bin/ps
>
> I subsequently tried installing the inetdtools version from cygwin1.3.1
> (1.3.2-11..) onto my 1.3.2 system,  and it doesn't solve the problem,  so
I
> think it must be a cygwin interactivity problem because but when I install
> 1.3.1 over it,  it works fine again..  it's very strange,  and the problem
> persists on all of the machines that we have updated (6 so far).  Perhaps
I
> should completely remove cygwin from the system and try a fresh install
> (rather than the upgrade)?  Strange
> Thanks for your time,
> Bruce
>
>
>
>
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: <cygwin@cygwin.com>
> Sent: Wednesday, June 13, 2001 6:13 AM
> Subject: Re: Inetd 1.3.2-14 problems
>
>
> > On Tue, Jun 12, 2001 at 02:47:35PM -0700, Bruce Dobrin wrote:
> > > Hi,
> > >
> > > I just upgraded to cygwin 1.3.2 including the 1.3.2-14 inetutils.
> > > Everything except rshd works as well or better than it did before.
But
> now,
> > > when I try an interactive rsh to my cygwin1.3.2 machine, I can't for
the
> > > life of me get beyond the passwd: prompt;  all I ever get is "Password
> > > Incorrect" regardless of what I type in....   I tried regenerating the
> > > passwd file (mkpasswd -d  and again with  mkpasswd -l)  and group
files
> and
> > > ui-config files ,  I tried changing the passwd file  /bin/bash to
> /bin/sh
> > > (which fixed a similar problem on earlier releases).  I didn't have
this
> > > problem with inetutils 1.3.2-11 since I went back to cygwin 1.3.1
(with
> the
> > > 1.3.2-11 inetutils) on one of my machines I no longer have this
problem
> > > there.   But I'd like to solve this problem on 1.3.2-14   has anyone
got
> any
> > > suggestions?
> >
> > For some reason I can't reproduce that. BTW, it's not related to rshd
> > but to rlogind since rsh connects to rlogind when an interactive
> > sessions is started. In theory you should see the same effect when
> > using rlogin on the client side.
> >
> > However, a typical reason for that problem is starting inetd under
> > an user account which may not switch user context.
> >
> > Try the following. Try to login from another machine interactively
> > using rsh or rlogin but don't type in a password when it asks for
> > a password. Instead of, simply do nothing.
> > Then start a local interactive session on the server side and call
> > `ps -e'. You should see something like that:
> >
> > $ ps -e
> >       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
> >      1648       1    1648       1648    ?   18 15:02:33 /usr/sbin/inetd
> >       892    1648    1648        892    ?   18 15:02:33 /usr/sbin/inetd
> >       816     892    1648       1572    ?   18 15:11:51
> /usr/sbin/in.rlogind
> >      1112     816    1112       1608    2   18 15:11:51 /usr/bin/login
> >      1240       1    1240       1240  con  100 15:11:54 /usr/bin/tcsh
> >       136    1240     136       1636  con  100 15:11:55 /usr/bin/ps
> >
> > Is the UID of inetd and the subsequent processes 18 as well for you
> > (which is the LocalSystem account)?
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin to
> > Cygwin Developer                                mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Want to unsubscribe from this list?
> > Check out: http://cygwin.com/ml/#unsubscribe-simple
> >
>


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple