Re: PATH altered for SSH client (SSH Secure Shell 3.0.1)
From: Mark Rafn (dagon@dagon.net)Date: 04/30/02
- Next message: Kenneth Simpson: "Re: Kerberos support"
- Previous message: Jim: "SSH or SSL?"
- In reply to: Chris Los: "PATH altered for SSH client (SSH Secure Shell 3.0.1)"
- Next in thread: Kenneth Simpson: "Re: PATH altered for SSH client (SSH Secure Shell 3.0.1)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: dagon@dagon.net (Mark Rafn) Date: 29 Apr 2002 23:14:49 GMT
In article <3CCD6B0A.9E6B25D0@trentu.ca>, Chris Los <clos@trentu.ca> wrote:
>When my ssh client connects to the server the client's PATH variable
>seems to mysteriously adopt some extra directory names along the way. I
>can't determine why these extra directory names are getting appended to
>the PATH and the client should not have them in the first place. My hunch
>is that somehow the client is adopting these PATH settings on login from
>the sshd2 process on the server side. But how?
I'm not sure I understand. The client's PATH is changing? If A is the
client and B is the server, you can do:
A$ echo $PATH
A$ ssh B
B$ exit
A$ echo $PATH
and see DIFFERENT results from the two echo statements? That seems very
very unlikely.
If you mean
A$ echo $PATH
A$ ssh B
B$ echo $PATH
then I'm surprised that you think this is a problem with ssh. I expect
your login process on B includes something that sets the path, and it's
working correctly.
-- Mark Rafn dagon@dagon.net <http://www.dagon.net/>
- Next message: Kenneth Simpson: "Re: Kerberos support"
- Previous message: Jim: "SSH or SSL?"
- In reply to: Chris Los: "PATH altered for SSH client (SSH Secure Shell 3.0.1)"
- Next in thread: Kenneth Simpson: "Re: PATH altered for SSH client (SSH Secure Shell 3.0.1)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
