This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem starting an executable from SSH
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 09 Apr 2012 16:43:17 -0400
- Subject: Re: Problem starting an executable from SSH
- References: <CAE4vMRd+-HGNC0OxkhybQUkVZFcB8nfrYex6kMp-vaRfBAG_2Q@mail.gmail.com> <CAE4vMRdG+eVAKLL5qos1wznUotbAAUw4szeY2NiCwirOSt=ZAA@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On 4/9/2012 4:35 PM, Jacques Guillou wrote:
I have some trouble using SSH to remotely start an executable on a
Windows XP which is running SSHD on Cygwin.
If I log into the windows machine using a simple "$ ssh
username@machine_name" command and then start the executable from the
BASH in interactive mode, then everything is fine, but I would
actually like to start the executable directly from the SSH
command-line with the following command:
$ echo "myExecutable" | ssh username@machine_name "bash -s"
The problem is that, in that case, my executable (a C/C++ compiler ".exe" file)
starts successfully but then reports a failure during the check of the
validity of the license.
So my questions:
- What actually happens when I log with SSH into a Cygwin machine ?
What scripts are started after the authentication has succeeded ?
- What could explain that the behavior of my executable is not the
same in both situations (started from interactive BASH session, or
started directly as input of "bash -s") ?
According to the 'ssh' manpage:
If command is specified, it is executed on the remote host instead of a
Since you've specified 'bash -s', the statement above applies. Add '-l' and
see if that helps.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple