Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <006a01c2b750$d70c7620$9700a8c0@michael> From: "Michael Hipp" To: References: <262990-22003138191816494 AT M2W090 DOT mail2web DOT com> Subject: Re: Bash PATH via ssh Date: Wed, 8 Jan 2003 14:02:06 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Thanks. I now have ensured that ~/.profile, ~./bash_profile, ~/.bash_login, /etc/profile all contain the lines: PATH="/usr/local/bin:/usr/bin:/bin:$PATH" export PATH But still when I do ssh 192.168.0.150 'echo $PATH' it returns only the windows path items. What am I missing here? Any help appreciated. Michael ----- Original Message ----- From: To: ; Sent: Wednesday, January 08, 2003 1:18 PM Subject: RE: Bash PATH via ssh I believe it's correct to assume that the invocation of bash via ssh is a login shell, not an interactive shell. Cygwin puts its path additions in /etc/profile. The corallary for a user would be ~/.profile, ~/.bash_profile or ~/.bash_login as the INVOCATION section of the bash man page suggests. Larry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/