SSH Path Bug

["Dominic Chambers" <dominic dot chambers at Swebtec dot com>]

Hi all,

Just wanted to report a bug I found:

Running commands via SSH causes windows executables to be given path priority, so that they run ahead of identically named UNIX executables. I found this while trying to use the find command as part of an SSH call. For example, assuming you have an SSH server set up:

? $ ssh localhost "find -true"
? FIND: Parameter format not correct

Here, the Windows find is being executed instead of the UNIX one. Alternatively

? $ ssh localhost "/bin/find -true"

Works fine. Also:

? $ ssh localhost "./myfindprog"
? FIND: Parameter format not correct

Also fails, assuming myfindprog looks like this:

? #!/bin/bash
? 
? find -true

On the other hand, things work fine provided you don't try to run your commands directly from the SSH process. So:

$ ssh localhost
Last login: Fri Apr 29 18:24:06 2005 from machine

Administrator@machine
$ find -true

is okay.



Thanks for a great product.

-- Dominic



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