I notice path is different between a ssh interactive session and a ssh remote command. When running remote command with ssh, the path does not include path to cygwin
Workaround: should manually add path to cygwin at the very beginning
e.g. into a shell script:
   #!/bin/sh
   PATH="/usr/local/bin:/usr/bin:/bin:$PATH" ; export PATH
   ....

I have MKS toolkit installed on my windows machine, thinking MKS shell were launched instead of cygwin shell because MKS in the windows system path. Perhaps a sshd server option or configuration setup to define cygwin shell as the default shell for remote commands?

Christopher Faylor wrote:
On Thu, Mar 10, 2011 at 06:32:00PM +0100, Philippe Scelers wrote:
Hi,
When setting a variable with the output of a command, the content of variable is not correct when passed through ssh command, but works fine within a ssh session. Looks like remote interactive session with ssh enter Cygwin (uname -s = CYGWIN_NT-5.1), but remote command with ssh does not (uname -s = Windows_NT)

And ideas would be appreciated!

My tests, executing same command line to highlight problem

The following remote ssh command fail ($a ends with '\r'):
ssh frgbuild@win32-xp-ps 'echo "`uname -a`" ; set -x ; a=`uname -r` ; b=`uname -rs` ; echo "a=$a=EOA=" ; echo "b=$b=EOB=" ; set +x'
Windows_NT WIN32-XP-PS 5 01 586
++ uname -r
+ a=$'5\r'
++ uname -rs
=EOA=
=EOB=dows_NT 5
' b='Windows_NT 5
+ echo $'a=5\r=EOA='
=EOB=' 'b=Windows_NT 5

Sure looks like you're not running the Cygwin version of uname here.
That would be consistent with \r\n line endings.

cgf

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



--
Philippe Scelers


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

Reply via email to