Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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, 14 Mar 2003 09:36:57 +0100 From: Corinna Vinschen To: "'cygwin AT cygwin DOT com'" Subject: Re: sec:unclassified Cygwin 1.3.21-1 problem with rsh command Message-ID: <20030314083657.GA27047@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: "'cygwin AT cygwin DOT com'" References: <751E281AA9DED31194FA0090274DFFBC012E3C04 AT fmbex003 DOT dsto DOT defence DOT gov DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <751E281AA9DED31194FA0090274DFFBC012E3C04@fmbex003.dsto.defence.gov.au> User-Agent: Mutt/1.4i On Fri, Mar 14, 2003 at 11:59:58AM +1100, Hill, Shane wrote: > Hi All, > > After updating to cygwin 1.3.21-1 the rsh command seems to have broken. Here is an example: > > rsh myhost -e "ls -l" > rsh: select: Bad file descriptor. > > Running rsh on its own (i.e. rlogin) seems to work okay. Read the mailing list archive. We had that yesterday. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/