On Fri, Feb 16, 2001 at 10:38:19AM +1100, Andrew Tridgell wrote:
> I actually like the name rsync :)
>
> I'd be very happy with a configure option that sets the default remote
> shell, and I don't mind a argv[0] check that knows about the name
> ssync, but I'd prefer for the package to still be called "rsync" as I
> think the name is well enough known that a change at this stage would
> not be a good idea.
I completely agree.
> btw, if you install as ssync you would have to also install as rsync
> (presumably a symlink to ssync would be used) as otherwise the remote
> operation of existing versions would fail.
Yes, I had no intention of removing the old name or changing the functionality
in any way other than setting the default rsh.
On Fri, Feb 16, 2001 at 11:35:01AM +1100, Michael James wrote:
> Why not just use ssh as the default if it is there?
>
> At present the configure scripts look first for remsh and set HAVE_REMSH
> Then the conditional definitions in rsync.h mean that RSYNC_RSH
> will get set to "remsh".
>
> At configure time why not look for ssh,
> add HAVE_SSH and conditionally set RSYNC_RSH to "ssh"?
>
> It worked for me.
I don't think that should be the default but I wouldn't mind a configure
option for it, maybe --default-rsh=<path>.
On Fri, Feb 16, 2001 at 05:25:09PM +0530, Ashwin Mansinghka wrote:
> The potential problem is the ssh binry location still differs from one
> unix variant to another and also depends on the compilation time flags.
>
> Unlike rsh which over the time has found a standard location, "ssh" still
> needs finds place in many places.
I figured it would just search for ssh in the configurer's PATH and compile
that in, and allow overriding with a --default-ssh=<path>. If no ssh is
found and no --default-ssh is specified it won't install ssync and ssync.1.
Hmm, I wonder if --ssh should be a runtime equivalent of -e and --rsh.
> Then again by default ssh has to be used with the pub key in the remote
> box and so on and so forth, like no pass phrase.
>
> I just hope having "ssync" will not create the notion that ssh once
> installed but not configured can work (like in case of scp where it
> prompts for a password and works)
>
> Will the manpage on ssync cover all these details too ??
No, I think that's beyond the responsibility of the rsync man page to
cover. People should consult the ssh manpage for that.
- Dave Dykstra
