On 17 Oct 2000, Jan?ke R?nnblom <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Recap:
> Im trying to syncronize my Windows NT servers to a central unix
> box running redhat 7.0. Previously I falsely stated that rsync 2.3.2
> work; it doesnt! It also bombs out on large transfers.
If the two machines are on a reasonably private network, then perhaps
you should use plain rsync rather than rsync-over-ssh. This will cut
out a large class of possible problems to do with ssh, fifos, sockets,
and NT.
In this case the data is not encrypted or authenticated, and the user
is identified only by a password challenge/response mechanism. So
it's roughly as secure as HTTP or SMB filesharing.
To do this, on the server run
# rsync --daemon
and create an rsyncd.conf. Then on the client say
# rsync OPTS /home/me rsync://server/mymodule
If you don't have root on the server then (contrary to old versions of
the man page) you can run the daemon as any user, except that you must
use a high-numbered port.
mbp@server$ rsync --daemon --port 8770 --config=~/rsyncd.conf
mbp@client$ rsync OPTS rsync://server:8770/mymodule
> Now there has been an indication on the list that ssh is to be
> blamed.
>
> I think i have tested every possible version of (free) ssh there is and
> noone that makes the problem go away.
Perhaps this is the compelling reason to implement rsync-over-ssl,
since it'll avoid relying on connections to an internal remote
shell. On buggy kernels they seem to have caused more than their fair
share of problems.
> Is there anybody that is running rsync with ssh on a windows
> machine with a large number of files and direcories?
Sorry, no.
--
Martin Pool, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
PGP signature
