comp.os.linux.networking

Michael Zawrotny wrote:
> Robert Harris wrote:
>> Michael Zawrotny wrote:
>>> Robert Harris wrote:
>>>> You need to run a rsync daemon on the server in any case; your choice is
>>>> whether to have it running all the time (from startup) or to be invoked
>>>> by inetd when an rsync client connects.
>>> Actually, you don't have to have rsyncd running on the server if you
>>> use ssh as the transport and the rsync binary in the user's path. My
>>> users routinely slog tons of data across our network without me having
>>> to setup rsync repositories for them.
>>>
>> Ah - but rsync on the server is run in daemon mode as rsyncd while it is
>> talking to your rsync client. The transport is the data transport; rsync
>> on the client figures out what needs transporting by comparing notes
>> with the rsync daemon on the server.
>
> That's one way to do it. If you "rsync -av server::some_module ." it will
> copy the contents of the defined module from rsyncd on the server to
> the current directory. On the other hand, "rsync -av server:my_dir ."
> will copy $HOME/my_dir and all of it's contents to the current
> directory. In that case, there is no rsyncd on the server, the user
> has to have login priveleges on the server and rsync has to be able to
> be found in $PATH. The difference is how you specify the remote
> location, one ":" or two.
>
>
> Mike
>
Yes, you are right.

Robert