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
Message-ID: <4272E677.CB0D7E3A@dessent.net>
Date: Fri, 29 Apr 2005 18:59:19 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SSH Path Bug
References: <AAE27702C6ACD84FA3BB03D6C04C2B67B5F6 AT swebtec-exchang DOT Swebtec DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Dominic Chambers wrote:

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

I would think this has more to do with how you set your path than
anything else.  What is $PATH in the case when it finds the windows
command, and what is $PATH when it finds the Cygwin command?  Cygwin
doesn't have any such notion of "path priority", it just searches the
path in order, so if it's finding the windows directory ahead of
/usr/bin you need to figure out how your path is being set and correct
it.

Brian

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