I recently built openssh 2.1.1p1, under solaris. I noticed that I had problems running scp. It seems that it could not find the executable on the remote end. This was odd, becuase it existed in /usr/local/bin, publically executable, and /usr/local/bin/was in the users' normal PATH (exported, even). So finally, I twiddled the source to make it call /usr/local/bin/scp, instead of just "scp". When I ran a strings on scp, it seems you have done a semi=similar hardcode of the path to ssh. /usr/local/bin/ssh turns up as a string in scp. So please do the same thing for the full path to scp, as well.
On Fri, Jun 23, 2000 at 12:44:15PM -0700, Philip Brown wrote:> I recently built openssh 2.1.1p1, under solaris. > > I noticed that I had problems running scp. It seems that it could not find > the executable on the remote end. > > This was odd, becuase it existed in /usr/local/bin, publically executable, > and /usr/local/bin/was in the users' normal PATH (exported, even). > > So finally, I twiddled the source to make it call /usr/local/bin/scp, > instead of just "scp".When you run configure, you can set the default path using: ./configure --with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin This is what I use, and it works fine for me. YMMV.
On Fri, 23 Jun 2000, Philip Brown wrote:> When I ran a strings on scp, it seems you have done a semi=similar > hardcode of the path to ssh. /usr/local/bin/ssh turns up as a string > in scp. So please do the same thing for the full path to scp, as > well.This is a FAQ. The paths to scp may be different on the client and the server, so harcoding them on the client won't help. The solution is to use the --with-default-path to include a path to scp on the server. -d -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller - http://www.mindrot.org/ | Email: djm at mindrot.org (home) -or- djm at ibs.com.au (work)
* Philip Brown <phil at bolthole.com> [000623 15:57]: | |So finally, I twiddled the source to make it call /usr/local/bin/scp, |instead of just "scp". I was lazy and took care of the scp path by symlinking /usr/local/bin/scp to /bin/scp. I did try to build it specifying the path first, but it did not seem to fix it. (portable open-ssh under slack 7+.) -Emily
no, this will not work, since the local ssh has no idea what the pathname for the remote 'scp' binary is. On Fri, Jun 23, 2000 at 12:44:15PM -0700, Philip Brown wrote:> When I ran a strings on scp, it seems you have done a semi=similar hardcode > of the path to ssh. /usr/local/bin/ssh turns up as a string in scp. > So please do the same thing for the full path to scp, as well.