New answers tagged rsync
libcurl does not support the rsync protocol. From the libcurl FAQ: Section 3.21 3.21 Protocol xxx not supported or disabled in libcurl When passing on a URL to curl to use, it may respond that the particular protocol is not supported or disabled. The particular way this error message is phrased is because curl doesn't make a distinction ...
Here's a simple way that doesn't preserve metadata: ssh server.example.com 'set -C; cat >/path/to/remote/file' </path/to/local/file You can do it with rsync with the right options. The return code will be 0 if the file exists, but you can find out from the verbose output instead. changes=$(rsync -a --ignore-existing --itemize-changes \ ...
Check if the file exists on the remote host first: if ! ssh remotehost [ -f incoming/DB1026910.sql ]; then scp DB1026910.sql remotehost:incoming/ fi
Preserve owner (-o, included in -a) is a feature only available to the superuser (root). Preserve group (-g, included in -a) is limited to the case where the user running rsync (on the destination site) is a member of the group. Rsync behaves this way because on most unix variants, these are the cases where it's allowed to set the target file's owner and ...
This is just a hunch, but are you running tests at the same time that you are deploying? The filenames look like temporary files that are being created and deleted while rsync is running.
depquid is very likely correct. I suggest you add this: --exclude='test.*.jar.?????' --exclude='.run-text.*.sh.?????' to the rsync command, maybe more; --exclude=app may also work as an alternative, depending on what you are doing. Btw, I think your implied -r and -p are redundant with -a.
Another way: $ noglob rsync server:/var/log/foo/2014-07-06-*.log . From zsh man page: noglob Filename generation (globbing) is not performed on any of the words.
You need to escape the special characters, e.g. $ rsync server:/var/log/foo/2014-07-06-\*.log . or $ rsync 'server:/var/log/foo/2014-07-06-*.log' . Or better, install url-quote-magic, e.g. autoload -Uz url-quote-magic zle -N self-insert url-quote-magic zstyle ':urlglobber' url-other-schema http https ftp mailto so that zsh will automatically do this ...
I suspect the --fake-super options. That tells rsync to store all the metadata information in extended attributes on each file. I suspect accessing those attributes are slow. Try a test run with rsync to a root without --fake-super. You can't reuse the same backup since the attributes won't match.
I had tried something similar to the answer above to copy dotfiles (pattern was: --include='.**' --exclude='*'), but found that some other excludes that I wanted were not actually being excluded. If you have other --exclude= flags you want to pass, use the following pattern: rsync -avz --exclude='path/to/exclude1' --exclude='path/to/exclude2' ...
You have run out of inodes on your backup drive. That's the out of space error you're seeing. Each file (basically) takes one inode. Unfortunately, with most filesystems there isn't a way to add more inodes, except mkfs. Example: with ext4, you pick the number of inodes created (at mkfs time) directly with the -N option, or as a ratio to the volume size ...
Top 50 recent answers are included