From: Warren Oates on 25 Mar 2010 07:45 In article <80vturFteoU1(a)mid.individual.net>, Jeffrey Goldberg <nobody(a)goldmark.org> wrote: > Note that I have a trailing slash on my source, but I don't on my > destination. (This is something that can trip people up when using rsync.) .... even people who have a pretty good understanding of rsync. Covered my Desktop up with 400 files, damn. -- Very old woody beets will never cook tender. -- Fannie Farmer
From: Ian Gregory on 25 Mar 2010 20:50
On 2010-03-26, Lewis <g.kreme(a)gmail.com.dontsendmecopies> wrote: > In message <slrnhqmbnf.t11.ianji33(a)zenatode.org.uk> > Ian <ianji33(a)googlemail.com> wrote: > >> He was talking about rsync over ssh whereas your command relies on there >> being an rsync daemon running on the server. So a more usual command >> might be more like: > > Ah, in that case it is: > > rsync -a --progress source server:sitedir > >> rsync -az -e ssh source server:sitedir > > I've never used the -e flag. OK, looking at the man page I see that ssh is typically the default so you would get a secure connection without having to specify it using the -e option. On the other hand, if you use the server::sitedir form then you will get an unencrypted connection to a remote rsync daemon *unless* you explicitly specify "-e ssh". Ian -- Ian Gregory http://www.zenatode.org.uk/ |