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: Thu, 26 Dec 2002 13:06:13 -0500
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: rsh problem - solved
Message-ID: <20021226180613.GA9340@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <917a993a15 DOT 93a15917a9 AT icomcast DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <917a993a15.93a15917a9@icomcast.net>
User-Agent: Mutt/1.5.1i

On Thu, Dec 26, 2002 at 09:00:21AM -0500, ROBERT CHUNG wrote:
>Just for your information, I found the solution.  On my server, I just 
>created /etc/hosts.equiv and put the IP address of client machines that 
>I am running rsh from.  Now my server is accepting rsh connections.  
>Thanks.

So, after lamenting that no one cares about helping you, the basic
problem would have been solved by reading the man page.  There's a moral
in there somewhere...

cgf

>> I just hope, someone now cares, since the problem doesn't seem to only
>> affect me.

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