Tag Info

New answers tagged

0

Unison is intrinsically peer-to-peer. This is precisely why a star topology is recommended: the tool does not have any notion of central server, so it's up to the user to enforce one. You can certainly use Unison in a peer-to-peer way, but there's no miracle: for every pair of machines (A,B), you need to pick one of the machines (say A) and create a profile ...


1

I have always used Unison in a star topology to synchronise my four machines. The reason for this is that it is not a versioning file system (like git for example), but rather a synchronisation tool. If you do opt for a distributed topology (which you will have to set by creating a configuration file for each device and synchronising all), you will ...


0

This did not work for me. I have jump hosting in my ~/.ssh/config Host 10.x.y.z User cloud-user HostName 21ct-dev1-pivot IdentityFile /path_to_21ct_dev1_key Host 21ct-dev1-* User cloud-user HostName %h.tx1.21ct.com ProxyCommand ssh 10.x.y.z -W %h:%p IdentityFile /path_to_21ct_dev1_key rsync -e "ssh" local_path ...


2

You can use a leading / to match only in the root of the transfer. Try this: rsync -avCz --delete-before --progress --exclude=/test/ /tmp/codebase/ . Here is the man page snippet for the leading /: if the pattern starts with a / then it is anchored to a particular spot in the hierarchy of files, otherwise it is matched against the end of the pathname. ...


0

Have you created the requisite directories? tar will not create non-existent directories. If not, this will do the trick. mkdir -p /backups/home The tar command will fail if any directories do not exist where you are attempting to create your tar.gz file, making it seem that anacron is not working. Checking the contents of /var/log/cron (Redhat-based ...


1

rsync include/exclude/filter rules can be a pain to work with, but are ultimately very flexible. Here is one way to do what you want: rsync --include-from=- /xapp/parsX/parsapp/object/ dest_dir <<EOF - getbackdate*autosys.sh - parssendevent*.sh + *.sql + *.pl + *.sh - * EOF The --include-from makes rsync read the patterns from stdin, without this ...


0

The manual says: -I, --ignore-times don't skip files that match size and time With more details: -I, --ignore-times Normally rsync will skip any files that are already the same size and have the same modification timestamp. This option turns off this "quick check" behavior, causing all files to be updated.


1

Though it is not the best answer, I found something that works by adding the following to my exclude-list.txt file: *syncTest/excludeTest/* I found the answer here: http://sourceforge.net/p/s3tools/bugs/81/ It is not intuitive, and I think it is a bug. I do not think that rsync has this problem, and it is probably specific to s3cmd. Very annoying! I am ...


1

Your real world example shows that you are missing the destination. If you want to copy to the current directory, use .: rsync -a root@mysite.net:~/testingrsync/test2.flv .


3

There are a number of things that could be done here. Note that none of the actually use hard links since they can only point to a full file. Using the btrfs filesystem opens up some vary useful possibilities here. Note that btrfs is currently (most recent version is v3.13) still experimental. However, its COW (copy-on-write) ability is perfect for this kind ...


4

By the looks of things, all you need to do is drop the quotes (line breaks added for clarity): rsync -avz \ david@machineB:/data/pe_t1_snapshot/20140317/t1_weekly_1680_0_200003_5.data \ :/data/pe_t1_snapshot/20140317/t1_weekly_1680_1_200003_5.data \ /data01/primary From the rsync man page: The syntax for requesting multiple files from a ...


0

readonly TGT=/export/home/david/dist readonly TGT1=${TGT}/primary readonly TGT2=${TGT}/secondary readonly MMAP_LOC=/data/pe_t1_snapshot readonly PART1='t1_weekly_1680_[03579]_200003_5.data' # shell globbing does readonly PART2='t1_weekly_1680_[12468]_200003_5.data' # the bulk of the work readonly F_LOC=BC readonly SSH="david@machine" #hoping the = works - I ...


1

The main problem with your script is that you're opening a separate scp connection for each file, that adds a lot of needless overhead. You could try something like this instead: #!/usr/bin/env bash readonly PRIMARY=/export/home/david/dist/primary readonly SECONDARY=/export/home/david/dist/secondary readonly FILERS_LOCATION=(machineB machineC) readonly ...


0

rsync takes care of: copying only the files that changed, ignoring files that you don't want copied (switch -C for example, which will exclude the same files that CVS would exclude in their repositories, although you can specify anything), recursively copying the entire structure of directories (of course, only the needed changes, not everything). It can ...



Top 50 recent answers are included