On Tue, Mar 29, 2005, Bill Campbell wrote:
> I ran into a problem at a customer's yesterday when I found that
> openssh no longer prepends the OpenPKG bin directory to the PATH
> on the server. Looking back through my archives, this appears to
> have happened between Release 2.1 and Release 2.2. This causes
> things like ``rsync -e ssh xxx'' to fail on the remote system or
> to find invalid configuration if there's a vendor supplied
> version of the program on the remote end that conflicts with the
> OpenPKG version of the program.
>
> The attached patch fixes this in what I think is a logical manner
> for OpenPKG Release 2.2, 2.3, and CURRENT.
Unfortunately, no, it doesn't. Well, to be precise, it "fixes" it
on those platforms where OpenSSH supports the --with-default-path
functionality only!
That's the reason why we explicitly removed any %{l_prefix} stuff there
(see http://cvs.openpkg.org/chngview?cn=19660) for cross-platform
consistency reasons. Because it is totally confusing if one some
platforms one magically has the %{l_prefix} in path by default set
by sshd(8) and on other platforms it isn't. Hence we decided to
intentionally not try to add %{l_prefix}/bin there at all and instead
have to life with the fact that there has to be either (1) a global
shell profile setting PATH correctly, or (2) a local shell profile
setting PATH correctly or (3) the user calls the command with an
absolute path.
All this I personally don't like very much, but to be honest, I do not
see a solution. Even hacking sshd(8) is not possible because the reason
why --with-default-path isn't working on all platforms is partly because
on those login(1) is used by sshd(8) (and this way PATH is reset by the
system after sshd forked off its child), etc.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
