On Wed, 22 Mar 2006 15:54:08 +0100, Joachim Schipper wrote: >So, if you want to go with rsync-a-tar-file, make sure it is not >compressed or encrypted beforehand. (Though running the rsync protocol >itself over an encrypted link is very, very good idea.) >
I do this for a client which has a zipfile of about 20MB which used to be delivered by courier from head office to retail stores. It had all the binaries used by the back-office computer plus stock files, inevntories etc. Now the zip files is copied from the master at head office to an OpenBSD box where it is unzipped to a directory. Then the stores connect at an appointed time and use rsync over ssh to update their local copies. Don't forget the C option in ssh (use -e "ssh -C" in the rsync options) which is too computationally expensive on a fast LAN but is ideal for lower speed links. For example, head office in my client has 1536/256 ADSL and the stores have 256/64 and it speeds up very well. HTH. Rod >From the land "down under": Australia. Do we look <umop apisdn> from up over? Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
