This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: STDOUT of non cygwin command lost (in automated ssh session)
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 17 Dec 2005 16:45:41 -0500
- Subject: Re: STDOUT of non cygwin command lost (in automated ssh session)
- References: <200512171952.jBHJqHoG029462@tigris.pounder.sol.net>
- Reply-to: cygwin at cygwin dot com
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. I can't speak for Corinna but,
sadly, I don't.
If you can't duplicate this problem with "off-the-shelf" components then
I'm afraid I'm going to have to say "It's a plink problem". We
sometimes have to make tradeoffs to achieve some benefits and maybe the
fact that plink (whatever that is) screws up stdout in a cygwin is one
of the tradeoffs.
cgf
--
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/