BibSonomy ::  tag ::

order by ( date | folkrank )

Você é daqueles que ainda usa FTP para copiar arquivos entre duas máquinas? Ei cara, já estamos no século XXI, este artigo nos introduz ao mundo do rsync, sinônimo de eficiência quando o assunto é cópia remota.

Cache files and other transitory data should be skipped. One way is via the --exclude-from=~/.rsync/exclude option, plus suitable file patterns in the exclude file. For more information, consult the EXCLUDE PATTERNS section in the rsync(1) man page. $ cat ~/.rsync/exclude .DS_Store .mozilla/**/Cache *.o

Cache files and other transitory data should be skipped. One way is via the --exclude-from=~/.rsync/exclude option, plus suitable file patterns in the exclude file. For more information, consult the EXCLUDE PATTERNS section in the rsync(1) man page. $ cat ~/.rsync/exclude .DS_Store .mozilla/**/Cache *.o

If you didn't include it, nothing in /usr/local would get included. Each filename is checked against this list, but in a recursive fashion. So if rsync is working on the file /usr/local/foo, it first looks for a pattern that matches /usr, then for a pattern that matches /usr/local, then finally for a pattern that matches /usr/local/foo. It uses the first pattern that matches. So, if you didn't include line 6, the search for /usr would fine line 8 and stop, thus excluding everything in /usr/local. Not what you want. I know that was confusing - recursion always makes my head spin...

If you didn't include it, nothing in /usr/local would get included. Each filename is checked against this list, but in a recursive fashion. So if rsync is working on the file /usr/local/foo, it first looks for a pattern that matches /usr, then for a pattern that matches /usr/local, then finally for a pattern that matches /usr/local/foo. It uses the first pattern that matches. So, if you didn't include line 6, the search for /usr would fine line 8 and stop, thus excluding everything in /usr/local. Not what you want. I know that was confusing - recursion always makes my head spin...

You can also put a file called .rsync-filter into the source directory and then you can use the -F option to rsync instead of listing the exclude rules on the command line every time. This is easier if you have to sync often, and you don't have to worry about the shell doing anything funny with wildcards.

You can also put a file called .rsync-filter into the source directory and then you can use the -F option to rsync instead of listing the exclude rules on the command line every time. This is easier if you have to sync often, and you don't have to worry about the shell doing anything funny with wildcards.

command="rdiff-backup --server --restrict-read-only /",from="kitty",no-port-forwarding,no-X11-forwarding,no-pty ssh-rsa AAAAB3NzaC1yc2EAAAAB[...] backup@kitty This entry in /root/.ssh/authorized_keys2 permits anyone with the specified key (i.e. backup@kitty) to connect with ssh from the host named kitty and issue the forced rdiff-backup command. It further restricts the ssh connection to eliminate port forwarding, X11 forwarding and a pty. The rdiff-backup invocation is also restricted to read-only operations starting from the root of the file system. NOTE: rdiff-backup 0.13.4 fails to support "--restrict-read-only /" without a patch. It works fine with sub-paths (i.e. /home), but you'll need my patch to backup from the root of the filesystem. If you'd prefer not to patch rdiff-backup then you can skip the "--restrict-read-only /" parameters -- it is up to you how paranoid you wish to be. If you have any troubles, this step is the one which has most likely caused you problems. Here

command="rdiff-backup --server --restrict-read-only /",from="kitty",no-port-forwarding,no-X11-forwarding,no-pty ssh-rsa AAAAB3NzaC1yc2EAAAAB[...] backup@kitty This entry in /root/.ssh/authorized_keys2 permits anyone with the specified key (i.e. backup@kitty) to connect with ssh from the host named kitty and issue the forced rdiff-backup command. It further restricts the ssh connection to eliminate port forwarding, X11 forwarding and a pty. The rdiff-backup invocation is also restricted to read-only operations starting from the root of the file system. NOTE: rdiff-backup 0.13.4 fails to support "--restrict-read-only /" without a patch. It works fine with sub-paths (i.e. /home), but you'll need my patch to backup from the root of the filesystem. If you'd prefer not to patch rdiff-backup then you can skip the "--restrict-read-only /" parameters -- it is up to you how paranoid you wish to be. If you have any troubles, this step is the one which has most likely caused you problems. Here