https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #7 from Filipus Klutiero 2014-03-14 04:39:59
UTC ---
Sorry if I was unclear, but I didn't mean to say that rsync's behavior should
be changed. I do believe that users would expect rsync to transfer directories
by default, but this does
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #6 from Kevin Korb 2014-03-14 03:41:18 UTC
---
Because the user probably doesn't want *.c to match files and directories. If
they want *.c recursively they probably need the include/exclude example that
is listed elsewhere. This is e
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #5 from Filipus Klutiero 2014-03-14 03:36:27
UTC ---
I understand that --recursive will consider directories. The problem is that
the example doesn't contain --recursive.
I managed to get my backup working, I was just pointing out the
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #4 from Kevin Korb 2014-03-14 03:16:04 UTC
---
Directories are only followed if you use -r aka --recursive. Note that in my
example I did so. However, if you added -r to your example you would get any
directory in the current directo
https://bugzilla.samba.org/show_bug.cgi?id=10495
Filipus Klutiero changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugzilla.samba.org/show_bug.cgi?id=10496
Summary: --itemize-changes always reports xattr changes with
--xattrs --fake-super
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: Linux
Status: NEW
Hi all,
rsync: rsync_xal_clear: lremovexattr("some/file/here","security.selinux")
failed: Permission denied (13)
I understand why these errors occur, but don't know the way to suppress or
resolve these messages.
Suggestions please. Pushing from v3.0.7 to a 3.0.6 server.
Regards,
Bryan--
On Tue, Mar 11, 2014 at 3:11 PM, Doug Robinson
wrote:
> I was wondering what folks thought of a proposal to enhance rsync to be
> able to create and maintain a cache of {filePath, 64-bit mtime, checksum}
> beforehand on both source and target systems and then use that cache later
> on when asked t
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #2 from Kevin Korb 2014-03-14 00:12:53 UTC
---
BTW, there is also a recursive example in the include/exclude pattern rules:
> The combination of "+ */", "+ *.c", and "- *" would include all
> directories and C source files but noth
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Hi
On Thursday 13 of March 2014 20:40:49 devz...@web.de wrote:
> What do "They" recommend instead?
>
> If it`s all about copying and network bandwidth is not an issue, you can use
> scp or whatever dumb tool which just shuffle the bits around "as is".
> rsync is being used when you want to keep
> Anyway, if "They" care about their data , "They" use checksumming for storing
> their data on disk, do "They" ? ;) silent bitrot on disks _does_ happen
I totally agree. Storage devices fail and if you need to know if the data is
the same then a checksum is your best bet. If you want to do you
What do "They" recommend instead?
If it`s all about copying and network bandwidth is not an issue, you can use
scp or whatever dumb tool which just shuffle the bits around "as is". rsync is
being used when you want to keep data in sync and if you want to save bandwidth
to handle that task. You
14 matches
Mail list logo
