ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anderson, Robert H - MWT" <>
Subject RE: ssh task - doesn't behave the same as command line ssh
Date Tue, 22 Apr 2003 17:14:20 GMT
This is true. The path that will be available to the sshexec task is the
same path that your sshd was compiled with. Run the following command to see
that path:

ssh username@hostname 'echo $PATH'

You will notice that this path is probably not the same path that you have
when you login interactively. There are a couple of options:

1. use the full path to executables not on sshd's PATH
2. put symlinks somewhere on sshd's PATH that point to the executables
3. recompile sshd with a different PATH

-Rob A

-----Original Message-----
From: Stefan Bodewig []
Sent: Monday, April 21, 2003 11:55 PM
Subject: Re: ssh task - doesn't behave the same as command line ssh

On Mon, 21 Apr 2003, Matt Reason <> wrote:

> So this task doesn't exactly act the same way as if you just logged
> into the machine.

But it probably does the same as if you used the non-interactive ssh
command line.

ssh doesn't parse ~/.bashrc (~/.kshrc, ~/.cshrc, ~/.tcshrc whatever
shell you use) when used in the non-interactive mode.  I'm not even
sure about ~/.profile (~/.login).


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message