Re: Bash PATH via ssh

2003-01-09 Thread Corinna Vinschen
On Wed, Jan 08, 2003 at 02:54:21PM -0500, Pierre A. Humblet wrote: > On Wed, Jan 08, 2003 at 02:02:06PM -0600, Michael Hipp wrote: > > Thanks. I now have ensured that ~/.profile, ~./bash_profile, ~/.bash_login, > > /etc/profile all contain the lines: > > > > PATH="/usr/local/bin:/usr/bin:/bin:$PAT

Re: Bash PATH via ssh

2003-01-08 Thread Pierre A. Humblet
On Wed, Jan 08, 2003 at 02:02:06PM -0600, Michael Hipp wrote: > 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 r

Re: Bash PATH via ssh

2003-01-08 Thread Michael Hipp
sing here? Any help appreciated. Michael - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> 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 v

RE: Bash PATH via ssh

2003-01-08 Thread [EMAIL PROTECTED]
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.