Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <262990-22003138191816494@M2W090.mail2web.com>
Reply-To: lhall@rfk.com
From: "lhall@pop.ma.ultranet.com" <lhall@pop.ma.ultranet.com>
To: michael@hipp.com, cygwin@cygwin.com
Subject: RE: Bash PATH via ssh
Date: Wed, 8 Jan 2003 14:18:16 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

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

Original Message:
-----------------
From: Michael Hipp Michael@Hipp.com
Date: Wed, 8 Jan 2003 13:09:59 -0600
To: cygwin@cygwin.com
Subject: Bash PATH via ssh


Hello, first post.

From a remote machine I'm doing something like:

    ssh 192.168.0.150 'echo $PATH'

All the path appears to be set to is the Windows system path. I've put path
amendments into /.bashrc and ~/.bashrc. As well as in the bash.bashrc files
in /etc.  Where do I put the path statements so they have effect when
invoked from ssh so I can get things like /bin into the path?

(I've read man bash invocation and searched the mailing list archives.)

Thanks,
Michael


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


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


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