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
To: <cygwin AT cygwin DOT com>
Subject: Issue when running non-cygwin programs with rsh
From: <bogossia AT nerim DOT net>
Date: Thu, 27 Feb 2003 23:08:27 CET
Reply-To: <bogossia AT nerim DOT net>
X-Priority: 3 (Normal)
X-Originating-Ip: [62.4.20.36]
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Message-Id: <20030227220824.6697262E7B@mallaury.noc.nerim.net>

Hello,

I've noticed that stdout doesn't seem to be properly
redirected when a non-cygwin program is executed via rsh.

You can easily observe the problem. For that, compile your
favorite hello world program with and without the no-cygwin
flag:

   home $ gcc -o hello_cygwin hello.c
   home $ gcc -o hello_nocygwin -mno-cygwin hello.c

Then run the two binaries with rsh:

   home $ rsh localhost hello_cygwin
   Hello world
   home $ rsh localhost hello_nocygwin
   home $

As you can see, the stdoud of the non-cygwin program is not
redirected to the remote terminal. This can be worked around
by piping stdout to the cat command:

   home $ rsh localhost "hello_nocygwin | cat"
   Hello world
   home $

Pierre Bogossian

___________________________________
Webmail Nerim, http://www.nerim.net/



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