I want to rsync a list of files (relative paths), not entire
directory trees. I know I can pass the list on the command line like
so:
cd /parent/dir
rsync -v -R relative/path/to/file.ext host:/parent/dir
I want to use --include-from=INCLUDE so I can pass a list of files
outside of
Hi.
The error I was getting was coming from the shell script and namely
the fact that rsync doesn't like the \ newlines.
Humm, this doesn't make sense: the \ are only managed by the shell and
suppressed by it *before* the call to rsync.
/usr/local/bin/rsync -vcrlnptgoxRz --delete -e ssh \
Hi,
...
rsync -av --exclude=/foo/test/dir1/ /foo/test serv2:/foo
and the exclude still does not work.
The following works:
rsync -av --exclude=/test/dir1/ /foo/test serv2:/foo
Why?
Because one should think the exclude pathnames are *relative* ones to
the destination directory.
In your
Example cmd: rsync -a --relative /home/me /dest
Source root: /home
I think it's instead:
Source root: /
Am i wrong?
Target root: /dest
I/E pattern: /home/me/foo/bar (note full path)
Source file: /home/me/foo/bar
Target file: /dest/home/me/foo/bar (note full path)
--
[EMAIL
Remember - we are talking about the transfer root, not the filesystem
root or partition root.
Yes.
The source transfer root is the source path with any trailing node
removed up to the last slash.
I see, but as soon as you have more than one source argument to rsync,
except when using
rsync -crzvv --password-file /etc/rsync.passwd --bwlimit=120
rsync://[EMAIL PROTECTED]/pub/critical_full_daily/*.* /STOR-1/
/var/log/rsync.xxx.pulls.xxx 21
...
Notice that *.* is used , i did this so that i can get all the files in
the directory. I have also tried * as the variable.
Then,
run this script in cron
00* * * * rsync -aucz /ftp/test/test1/
/ftp/test/test1/test3/
Beware:
1. This will create the first time: /ftp/test/test1/test3/test3, then
/ftp/test/test1/test3/test3/test3 the second time and so on till filling
up the disk.
It would
On Tue, 15 Jun 2010 18:58:36 PDT Marc MERLIN wrote:
The /data symlink is clobbered and replaced by a directory. Very bad!
Any idea what's going on here and is there a magic flag to work around this
problem?
I thing you simply need the --no-implied-dirs flag.
Francis
--
Please use
On Sat, 09 Jul 2011 15:04:24 +0200 Louis-David Mitterrand wrote:
Is there also a pure rsync solution (without any shell loop) maybe based
on --include/--exclude?
I thing the following will do:
cd /backup/current/home
rsync -av --delete \
--include '/*/' \
--include
disabled for local transfer or --whole-file
cd+ ./
cd+ b/
f+ b/bar
total: matches=0 hash_hits=0 false_alarms=0 data=0
sent 115 bytes received 38 bytes 306.00 bytes/sec
total size is 0 speedup is 0.00
Francis Montagnac
--
Please use reply-all
On Tue, 15 Nov 2011 23:49:18 +0100 Brian K. White wrote:
nj2:/opt/x # rsync -avvvn --force --delete --include=/tmp
--include=floof/ --exclude='*' /tmp/. co4::root/tmp/.
Detail: /tmp being the root of the transfer, --include=/tmp is
wrong because it refers then to /tmp/tmp.
I thing you can
On Tue, 05 Jun 2012 23:18:24 +0200 Clint Olsen wrote:
Ok, itemize changes prints out some info for each file, and it looks like:
...
I did a quick search on this switch and someone was bitching that the
fields were not easy to decipher w/o reading the source code :)
Wrong: the
On Fri, 02 Nov 2012 19:32:14 +0100 Cuong X Dang wrote:
rsync error: timeout in data send /received (code 30) at ioc (140)
...
rsync=/usr/bin/rsync -aviHz --delete --progress --timeout=10
This is a timeout of 10 seconds. Try to increase it.
--
francis.montag...@inria.fr
--
Please use
Hi.
On Wed, 21 Nov 2012 11:41:48 +0100 kamleshverma wrote:
In mail server /mail_home folder having all user's mailbox and size of
mail_home is 345 GB and in backup server I have assign 450 GB for
mail_backup drive.
That lets 105 GB of free space for the temporary copy done by default
On Wed, 21 Nov 2012 13:32:17 +0100 kamleshverma wrote:
Yes, Drive showing full. actually I created LVM for backup..
I don't know LVM well, but if you use it to keep snapshots of your
volume that explain your problem. At worsed, ie: if every files have
changed between two runs, you will need
Hi.
On Fri, 11 Jan 2013 03:08:13 +0100 Allen Supynuk wrote:
To make matters worse, the file is on a read-only snapshot mounted
through NFS. In any case root squash is in effect, so super-user is
out.
Why not mounting this no_root_squash?
Is it not wrong to have partial archives (missing
Hi.
On Mon, 11 Mar 2013 23:17:06 +0100 Mark Casey wrote:
On 3/11/2013 4:18 PM, Mark Casey wrote:
...
rsync -nav --no-t --numeric-ids --relative --include='*/' --exclude='*' \
/media/mnt/files /media/backups/mnt/
...
I was wrong. The command I listed is working after all, I just wasn't
Hi.
On Fri, 05 Apr 2013 19:04:50 +0200 Bob von Knobloch wrote:
At the moment I also get a complete list of all directories that lie
under in rsync's target, whether they are updated or not.
Perhaps because the modify time of those directories changes. Adding a
--itemize-changes option
On Sat, 06 Apr 2013 14:52:59 +0200 Bob von Knobloch wrote:
Thank you, it wasn't timestamps, but group id inconsistency (the source,
in this case is a Windows box, ids are always tricky).
...
I must rewrite the group ID after transfer, because the destination gid
(special group), is neither
Hi.
On Fri, 03 May 2013 11:45:24 +0200 bert wrote:
When running the script from upstart, rsync exists with a error 14,
some error that has something to do ipc codes. (What are ipc codes?)
I think I saw that already. It was a bug in a library that assumes
that stdin stdout stderr are opened.
Hi.
On Thu, 30 May 2013 22:17:24 +0200 Christoph Biedl wrote:
there's an old proposal to exclude a directory and its subdirectories
from being backed up and the like, ...
You can achieve that already with the -F option of rsync. Create a
.rsync-filter file in the directories you want with the
Hi
On Wed, 03 Jul 2013 11:00:38 +0200 Grant wrote:
These are both specializations of the generic --filter='merge filters.txt'
filter option. See the rsync man page for the gory details.
That's a great feature and I think it should be referenced in some way
under --include-from and
On Thu, 05 Sep 2013 20:04:21 +0200 Stier, Matthew wrote:
The only time I've seen where some kind of threading would have help,
is I was trying to transfer hundreds of gigabytes of data across a
gigabyte link. ...
There is another rather common case I think where this would help:
when the
Hi.
On Wed, 16 Jul 2014 23:24:45 -0700 Don Cohen wrote:
So another question/suggestion - if you save the output it would be
nice to be able to pipe it back into rsync as the list of files to
be transferred - which would be easier if there were a switch to do
the translation above. ...
Not
Hi.
Try perhaps to copy /etc/localtime in the chroot, for example with:
cd /
rsync -LaR etc/localtime PATH_TO_THE_CHROOT/
Francis
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
On Tue, 19 Aug 2014 02:29:35 -0400 Kevin Korb wrote:
Nothing in your example involves the rsync daemon or a chroot.
Except the PATH_TO_THE_CHROOT/
Anyways, what happend when you did that and what did you expect to
happen instead?
I suspect that the rsync daemon is calling localtime(3) in the
Hi
On Sat, 28 Feb 2015 06:41:59 +0300 Дугин Сергей wrote:
rsync -a --exclude=tmp/* /home/ /backup/home/
If the folder /home/tmp/ is many millions of files, rsync
think of this folder can be seen through the lsof -p PID
Or strace yes. It seems that rsync does an lstat for any file before
Hi,
On Mon, 13 Apr 2015 12:59:07 -0400 Kevin Korb wrote:
Hmmm, according to my interpretation of the man page (I am on 3.1.1)
that is supposed to work however when I test using the -/
/etc/passwd example the / seems to have the same effect as commenting
the line. I get /etc/passwd copied
On Mon, 13 Apr 2015 13:45:18 -0400 Kevin Korb wrote:
The +/- syntax absolutely works in an --exclude-from or --include-from
file I use it all the time. However, apparently the -/ syntax does
not work there.
So, I am not sure if the man page is wrong or if this feature just
isn't working
Hi
On Wed, 29 Apr 2015 14:23:56 +0200 Frantisek Hanzlik wrote:
Now I still do not understand why does not work this switch form:
--chmod=D=775,F=664
This is not the proper syntax: suppress the = signs before the modes:
--chmod=D775,F664
--
Francis
--
Please use reply-all for most replies
Hi.
On Sun, 07 Aug 2016 20:00:46 +0200 Joó Ádám wrote:
> Can anyone at least confirm that this is an issue or if I’m doing
> something wrong?
This seems a bug yes. I checked that it shows up also when one uses
the --times option instead of --checksum.
Using -i (--itemize-changes) seems the
On Thu, 23 Feb 2017 18:07:20 + David Epstein wrote:
> I will try the modification
> rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’
> SOURCE/ TARGET/
The 'protect /.*’ is useless: unlike the shell, rsync interprets *
simply as a path component, regardless thus
On Fri, 24 Feb 2017 07:51:56 +0100 francis.montag...@inria.fr wrote:
>> Unfortunately, the output from —dry-run is still likely to be
>> sufficiently extensive that looking over it won’t be a completely
>> certain test.
> Then redirect to a file and grep deleting in this file.
Given the
Hi.
On Thu, 23 Feb 2017 11:07:16 -0500 Kevin Korb wrote:
> I hate to say it because it goes against my normal advice but this is
> one instance where using a * in the source parameter would help...
I totally agree.
I thing that using a protect filter achieves this goal (without using
a *
Hi
On Sun, 30 Oct 2016 20:06:00 +1300 Samuel Williams wrote:
> But it's also a surprise that backslash escape sequences don't work
> according to intuition of how commands are normally executed. If you
> supplied the string in -e to system, it would work as expected..
> Unfortunately, this is
35 matches
Mail list logo
