Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 27 Mar 2002 10:54:09 +0000
Message-ID: <5922-Wed27Mar2002105409+0000-starksb@ebi.ac.uk>
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Jonas Eriksson <jonas_eriksson AT home DOT se>
CC: cygwin AT cygwin DOT com
Subject: bash failed to initialize on telnet/rsh/rlogin server
In-Reply-To: <718198F862F1D411B10F0002A50A4DB1059FE8DF@e90wwce3.dx.deere.com>
References: <718198F862F1D411B10F0002A50A4DB1059FE8DF AT e90wwce3 DOT dx DOT deere DOT com>

On Tuesday 26 Mar 02, Polley Christopher W writes:
> I'm trying to get inetd set up for telnet/rsh/rlogin on my machine and have
> everything going up to the point that after login.exe gives the motd to the
> telnet client, a dialog window pops up on the server titled "bash.exe -
> Application Error" and says "The application failed to initialize properly
> (0xc0000022)."  Acknowledging the dialog closes the connection with the
> client.
> 
> I have telnetd working on another machine (NT4) but haven't been updating it
> to the latest cygwin packages.  The new machine is running W2K, was updated
> this afternoon, and although there are 56 differences in the cygcheck -c
> outputs, these are the ones that seem relevant to me: (differences
> highlighted with *)
> 
>         <system that doesn't work>              <system that works>
>         Cygwin Package Information              Cygwin Package Information
>         Package             Version             Package             Version
> *       bash                2.05a-3             bash                2.05a-2
> *       cygwin              1.3.10-1            cygwin              1.3.6-6
>         inetutils           1.3.2-17            inetutils           1.3.2-17
>         login               1.4-3               login               1.4-3
> 
> Both are running with ntsec, and have identical passwd and group files (both
> from the domain server, passwd trimmed to a couple users plus the usual
> system accounts)

This happened to me on NT4 when I upgraded to cygwin-1.3.10, and was
*not* using ntsec.  Using ntsec fixed it.  Is ntsec set early enough
for inetd?  (And are you rebooting when making changes?)  Does the
inetd service have sufficient user rights?  Is everything
readable/executable that needs to be?  Double check your passwd/group
entries with latest mkpasswd & mkgroup, possibly even from the latest
inst snapshot.  Make sure the user's groups are all in /etc/group.

These have all been suggested in the past as possibly causing this
error.

Why I get the error with nontsec and not with ntsec, is still mystery,
but Corinna has been on holiday. :-)

Regards,
David


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