On Fri, Sep 15, 2000 at 12:38:50AM -0400, Pierre Abbat wrote:
> >rsync -avuzb --rsh=/usr/local/bin/ssh --exclude �*~�
> >[EMAIL PROTECTED]:/home/rob/toppage .
> >rsync -Cavuzb --rsh=/usr/local/bin/ssh .
> >[EMAIL PROTECTED]:/home/rob/toppage
...
> Don't use . in a shell script unless you have a cd before it. Otherwise you
> don't know what . is.
>
> The first directory should not end in a slash; the second should. At least
> that's how I have it, and it works.
> rsync -avuze ssh /home/phma/dir remote:/home/phma/
> rsync -avuze ssh remote:/home/phma/dir /home/phma/
The ending slash on the source is usually very significant to rsync, but an
ending slash on the destination doesn't make any difference (assuming the
destination directory already exists). I say "usually" because it doesn't
actually make any difference if the source is ".". as in Robin's case. The
thing that the trailing slash does on the source is to skip appending the
base directory name of the source to the ending path. Thus in your example
rsync -avuze ssh /home/phma/dir remote:/home/phma/
is equivalent to
rsync -avuze ssh /home/phma/dir/ remote:/home/phma/dir
or
rsync -avuze ssh /home/phma/dir/ remote:/home/phma/dir/
If the source is "." all it will do is append a "./" which has no effect.
- Dave Dykstra
