delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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 |
Message-ID: | <000701c459b1$38a5f420$3400a8c0@ug.btx.dtag.de> |
From: | Guettich AT t-online DOT de (=?iso-8859-1?Q?Ulrich_G=FCttich?=) |
To: | <cygwin AT cygwin DOT com> |
References: | <001501c45952$4be05580$3400a8c0 AT ug DOT btx DOT dtag DOT de> <20040623193114 DOT GA572401 AT Worldnet> <000701c4596b$586c93e0$3400a8c0 AT ug DOT btx DOT dtag DOT de> <20040623221611 DOT GA1020225 AT Worldnet> |
Subject: | Re: Re(3) rlogin problems |
Date: | Thu, 24 Jun 2004 08:05:11 +0200 |
MIME-Version: | 1.0 |
X-Seen: | false |
X-ID: | TJ4KBsZTweoOFAjR2EVCVRk4CH4kCyQtUZ-uiy1AW7mpfMUaS+rMo0 |
> > Thank you, Pierre. I have immediatetly installed the new cgwin1.dll from > > your snapshot on my PC1 and made the following observations: > > > > 1. rlogin to PC2 worked fine! > > > > 2. now I installed the new cygwin1.dll also on PC2 and tried again: rlogin > > from PC1 to PC2 or vice versa. Unfortunately, now we seem to have problems > > on the receiver side: the rlogin fails and an ugly Windows error message (in > > my case in German) comes up with a content like "Application not valid ...". > > The output of "inetd -d" does not show any errors. > > > > What's up now? Sorry for the inconvenience! > > What happens when you rlogin from PC1 to PC1? That was my test and it > worked. > It's unlikely that the latest patch is causing the problem you see, > but of course there have been several changes since the last official > release. When I rlogin from PC1 to PC1 I have the same Windows error message - which btw shows an error for "login" - and a "closed connection" output in the Cygwin window. I have now recognized that "rsh PC1 ls" also fails. Again the Windows error message comes up, now indicating an error of "bash". Ulrich -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |