Message-Id: <200512181446.jBIEkj1h011614@tigris.pounder.sol.net>
From: cygwin AT trodman DOT com
To: cygwin AT cygwin DOT com
Subject: Re: STDOUT of non cygwin command lost (in automated ssh session)
In-reply-to: <20051217214541.GA18982@trixie.casa.cgf.cx>
References: <200512171952 DOT jBHJqHoG029462 AT tigris DOT pounder DOT sol DOT net> <20051217214541 DOT GA18982 AT trixie DOT casa DOT cgf DOT cx>
Date: Sun, 18 Dec 2005 08:46:44 -0600
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sat 12/17/05 16:45 EST cygwin AT cygwin DOT com wrote:
> On Sat, Dec 17, 2005 at 01:52:17PM -0600, Tom Rodman wrote:
> >background (why plink is used):
> >
> >We have a wrapper script that runs plink to start a localhost ssh
> >session w/password authentication.  This wrapper script is designed to
> >run a command after the ssh login.  (We also have a similar cygwin
> >expect script.) The benefit- network drives are writable.  These
> >wrapper scripts are used in crontabs.  The problem is not with these
> >scripts
> 
> You seem to be expecting that the people whom you'd like to debug your
> problem would know what "plink" is.  

Sorry, it's closely related to putty.  I don't have a good link
specifically for plink..

  http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html

> If you can't duplicate this problem with "off-the-shelf" components 
--snip

I will try to duplicate the problem using a short expect script
instead of plink - may take a few days; I'll post to this thread.

--
thanks,
Tom 

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