On Wed, May 23, 2001 at 08:44:38AM +1000, Martin Pool wrote:
> On Tue, May 22, 2001 at 08:19:46AM -0500, Dave Dykstra wrote:
> > Yes, please submit a patch. I'll make sure it gets in. I would use it too.
> >
>
> Yes, that sounds good to me too.
>
> > Please make sure it can accept semicolons and spaces; I currently always
> > modify the source to set RSYNC_NAME to "PATH=/opt/exp/bin:$PATH; rsync".
> > (I realize that doesn't work for all shells but it is very rare around here
> > for somebody to use a login shell that isn't compatible with bourne shell).
>
> Would putting PATH=/opt/exp/bin:$PATH in /etc/profile fix this? I think it's
> executed by ssh/rsh for non-interactive logins, but I'm not sure. If it is,
> I might add that to the FAQ. (I realize you might have good reasons not to
> do it in this particular case. I'm just curious.)
No, neither ssh nor rsh read /etc/profile, although ssh reads
~/.ssh/environment. Even if they did it wouldn't matter because it is
impractical to modify /etc/profile on all the systems that I install
rsync on, there's just too many. Setting RSYNC_NAME to include the PATH
variable rather than setting it to an explicit path to /opt/exp/bin/rsync
allows it to work also to systems that don't have the /opt/exp tools but do
have rsync in the default PATH.
- Dave Dykstra
