Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 29 Jan 2001 21:14:12 +0100 From: Corinna Vinschen To: cygwin Subject: Re: rshd/rsh problem Message-ID: <20010129211412.C5879@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <4 DOT 3 DOT 1 DOT 2 DOT 20010129082548 DOT 00b94e90 AT postoffice DOT pacbell DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.1.2.20010129082548.00b94e90@postoffice.pacbell.net>; from haydenr@interwoven.com on Mon, Jan 29, 2001 at 08:41:30AM -0800 On Mon, Jan 29, 2001 at 08:41:30AM -0800, Hayden Ridenour wrote: > I've run into another snag with rshd. When I rsh into my Win2K machine and > run a local command, that works. However, if I rsh into my Win2K machine > to rsh back out to another machine, that generates the following message: > > rsh: shell/tcp: unknown service > > I first discovered this trying to launch rsync on the Win2K box but have > reduced the test case to: > > # rsh win2k "rsh solaris1 date" > > All of these command work from a local bash shell on the Win2K box and from > rlogin sessions. > [...] Sure. You started inetd from LocalSystem account. A non interactive rsh has no chance to change user context since no password is given. So the started subshell is running under LocalSystem account either. Unfortunately, LocalSysterm has absolutely and unchangable _no_ chance to create an outgoing network access. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple