Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: SSH Path Bug Date: Fri, 29 Apr 2005 21:00:56 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: Content-class: urn:content-classes:message From: "Dominic Chambers" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j3TK1E69022639 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/