On Thu, 2003-09-04 at 17:46, Bill Campbell wrote: > On Thu, Sep 04, 2003, Roger Oberholtzer wrote: > >On Thu, 2003-09-04 at 05:38, Bill Campbell wrote: > ... > >> There's no relationship between rsync and the berserkely ``r'' commands > >> beyond the first letter of the name. > > > >I thought (possibly incorrectly): rsync uses rsh on the client side to > >do the actual talking to the server. Try running rsync without rsh > >installed. And it expects rshd on the server side. You 'could' also run > >an rsyncd instead of a rshd on the server side, but us clients would be > >connecting on a different port (873). As we are not doing do, we are > >talking to your rshd. All rather Berkeley. > > ``rsync -e ssh ...'' uses secure shell for the transport.
Is anyone doing this to sync the sxs? > We often use rsync in server mode which has its own server for things like > updating djbdns data files on backup DNS servers where each domain master > has its own entry in the rsyncd.conf file restricting access to one > directory, and to the IP address (or CIDR block) of the updating server. Which is the way things should be. But rsync 'out of the box' and using the command lines I have seen in sxs update scripts use none of this. I just installed SuSE on a laptop and wanted to rsync to it. That is when I discovered that the rsync daemon was not relevant, in favor of rshd. _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
