Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	SSH Path Bug
Date:	Fri, 29 Apr 2005 21:00:56 +0100
MIME-Version:	1.0
Message-ID:	<AAE27702C6ACD84FA3BB03D6C04C2B67B5F6@swebtec-exchang.Swebtec.com>
From:	"Dominic Chambers" <dominic DOT chambers AT Swebtec DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
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 AT 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/

- Raw text -