rsync -e ssh does not work well

[heikkila at mappi.helsinki.fi]

These are the facts: 
The copy was successfull, the authentication 
was made by ssh protocol, but rsyncd.log was
not updated on the server side. The previous 
is not fatal, but I believe should do something to 
confirm that it was ssh protocol that made the 
copy, perhaps by looking at the traffic.
After that we should look at the various 
forms of copy operations, how they work. 
Do you agree? Currently I have not possibilty
to continue during weekend and not possibly on monday. 

Following Scholten's page is very straightforward 
and quickly done, so you may find time some to
make your tests, too.

I took his "full version"  zip file and used 
c:\rsync as program directory.  This installation 
did not interfere with any other setup, for
instance my machine's  F-secure ssh does not 
contain ssh.exe, but ssh2.exe, instead. 
So F-secure did not take part.   The newer ssh 
seemed to create it's own .ssh subdirectory. I 
did not yet here go further to test the 
authentication options to be applied in 
batch type  operations. 

Kauko 
Lainaus Michael King <mikkel at market-research.com>:

> Kauko,
> 
> Does this mean you have been successful with rsync -e ssh ?
> 
> Mike
> 
> At 08:26 PM 10/25/2002 +0300, Kauko Heikkila wrote:
> 
> >----- Original Message -----
> >From: "jw schultz" <jw at pegasys.ws>
> >To: <rsync at lists.samba.org>
> >Sent: Friday, October 25, 2002 5:04 PM
> >Subject: Re: rsync -e ssh does not work well
> > > >
> > > > rsync -trvuz   file.wrk uname at servername::uname-html
> > > > works, but
> > > > rsync -trvuz  -e ssh  file.wrk
> > > > uname at servername:public_html/
> > > > does not.
> > > >
> > >
> > > The version of rsync on you laptop 2.4.6? is quite old
> >and
> > > many bugs have been fixed since.  Normally we would
> >suggest
> > > you start by upgrading to the latest version, either
> >2.5.5 or
> > > CVS.  Supporting obsolete bugs is a pain.
> > >
> >I made clear progress after  installing a newer version.
> >The laptop is now in someone else's use, but
> >I installed rsync on my desktop
> >following Robert Scholten's minmalist approach- page
> >http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html
> >The version coming from his page is
> >2.5.1 and the protocol version is 25.
> >
> >Both
> >rsync251-2.exe  -trvuz   file.wrk
> >uname at servername:public_html/
> >and
> >rsync251-2.exe  -trvuz -e ssh file.wrk
> >uname at servername:public_html/
> >
> >seem to do the same, because there was a setup file
> >rsetup.bat
> >that sets RSYNC_RSH to SSH.EXE
> >
> >The ssh also came from Robert Scholten's
> >pages here and might be a reason, who knows.
> >
> >It seems to work, since sshd logs the event in the server.
> >I cannot see any other log records,
> >especially not in the normal rsyncd.log of the Linux
> >server.
> >The fact is that the file is  really transferred. Some
> >tests
> >should actually  be made to confirm that it really
> >is the ssh protocol, but I am positive.
> >
> >Thanks
> >
> >Kauko
> >
> >P.S.
> >Unfortunately I did not yet find any log in windows and I
> >could
> >not pipe the resulting tty lines in NT window.
> 
>