search for: va_public

rsync is great for syncing 2 directory trees, but I want to maintain a master source tree on one machine and copy that to multiple machines. i.e. basically what rdist does The only way I can see of doing this with rsync is to have multiple cron jobs 0 * * * * rsync ... machine1:... 0 * * * * rsync ... machine2:... ...and so on. Is there a more elegant/compact way of doing this? Thanks

rsync 2.5.6 If I turn on the --backup (and --backup-dir and --suffix) options and rsync a tree like rsync --backup ... -av --delete dir1/ user@machine:dir1 I dont see the 'deleting ...' message in the output, but if I delete a file in the source tree, it DOES get deleted from the target tree. If I remove the '--backup' option, I do get the 'deleting ...' message.

I got used to rsync's -v --progress option so much that I used it instead of rcp even to simply copy files across the network. I dont like software that doesnt talk to me! :-) I like the percentage bar that --progress gives! To my surprise, I found that, when dealing with 1GB+ files, rsync is 4-5 _times_ slower than rcp. Yes, I know that rsync is optimized for sending deltas to a file

When I do rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/dir3 machine:/dir1/dir2/dir3 I get /dir1/dir2/Backup/dir3/... /Backup/dir3/dir4/... i.e. the tree under 'dir3' (my source tree) gets created under .../Backup. This is fine. But when I do the same thing with a single file like rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/file