Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Reply-To: Cygwin List <cygwin@cygwin.com>
Message-Id: <6.1.0.6.0.20040806105531.033469a0@pop.prospeed.net>
X-Sender: 
Date: Fri, 06 Aug 2004 11:06:12 -0400
To: "David E. Meier" <dev@eth0.ch>, "Cygwin List" <cygwin@cygwin.com>
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
Subject: Re: Redirect stdout from SSH
In-Reply-To: <3552.217.162.71.141.1091799815.squirrel@217.162.71.141>
References: <1614.217.162.71.141.1091552632.squirrel@217.162.71.141> <6.1.0.6.0.20040803172459.0338a528@pop.prospeed.net> <3552.217.162.71.141.1091799815.squirrel@217.162.71.141>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 09:43 AM 8/6/2004, you wrote:
>I got it working when standard input is also set to be redirected. Does
>anyone have an explanation of this?


No, sorry.  At least not without some details of what you did.  Like I said,
the simple example I put together worked fine for me so it seems clear that
there's a detail which is missing that accounts for the behavior you're 
seeing.  Did you try that example?  If you need me to, I can send the code,
though it just invokes 'ssh' as you describe via 'system()'.  

If you can point to how your example is different than mine or provide a simple example that shows the problem, that might help.


>> At 01:03 PM 8/3/2004, you wrote:
>>>Hello list,
>>>
>>>I am writing a program in C# that calls some cygwin programs and
>>> redirects
>>>the standard output and error to a textbox. This works excellent with
>>>calls like "ls -al" or rsync.
>>>
>>>However, I cannot read the output generated by SSH. When I issue a
>>> command
>>>like "ssh user@host ls -al" I can observe some network action but the
>>>application stalls, uses 100% CPU and never spits out something. The same
>>>command in the cygwin shell executes with the result expected. Since I
>>> use
>>>public key authentication SSH is not waiting for any login information.
>>>
>>>Is this a configuration issue of SSH? Thanks for any help. Dave.
>>
>>
>> Not AFAICS.  A small C program that invokes Cygwin's 'ssh' via 'system()'
>> with 'ls -al' works fine for me.  Does that work for you?

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

