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: Fri, 25 Oct 2002 18:02:14 -0400
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with rsh
Message-ID: <20021025220213.GA187817@WORLDNET>
References: <3DB9AD4E DOT 10407 AT Salira DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DB9AD4E.10407@Salira.com>
User-Agent: Mutt/1.4i

On Fri, Oct 25, 2002 at 01:45:02PM -0700, Andrew DeFaria wrote:
> I've run into a major problem using rsh. Note that I've been using rsh 
> successfully for a while and many people here depend on being able to 
> rsh into the server. However now I get:
> 
> $ rsh server id
> server.mydomain.com: Permission denied.

No such problem here when the home directory (from passwd)
is on a local drive 

~> rsh localhost id
uid=11054(PHumblet) gid=10513(Domain Users) 

However

~> rsh localhost id
PHumblet.mydomain.com: Permission denied.

when the home directory is on a network drive.
This is to be expected if the network drive has security.

> uname -a
CYGWIN_NT-4.0 PHumblet 1.3.14(0.62/3/2) 2002-10-24 10:48 i686 unknown

Pierre

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