Displaying 20 results from an estimated 100 matches similar to: "itemize() needs to use CHMOD_BITS (patch)"
2003 Feb 08
1
compare st_mode & 07777, or Aix dirs always differ
Under Aix directories have the mode 024xxxx instead of the customary
04xxxx. Because of this when you sync a directory to or from an Aix
system it's never up to date.
Here is a patch which fixes this. It causes rsync to look at only the
bits that chmod actually influences, 07777, when deciding whether or not
the modes differ.
I was surprised there wasn't an existing constant for 07777,
2006 Jun 02
3
[PATCH] --omit-dir-changes, qsort<>mergesort issues
Hi all,
I recently ran into some problems with rsync. My plan is to renew some of
our old administration concepts from early 90's, I already replaced rdist
with rsync a few years ago.
Because of the rdist legacy, the current method requires synchronizing
files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep},
which in turn are prioritized by a tool that just symlinks
2003 Feb 19
0
FW: compare st_mode & 07777, or Aix dirs always differ
>jw schultz [mailto:jw@pegasys.ws] wrote:
>On Fri, Feb 07, 2003 at 11:15:57AM -0500, Roderick Schertler wrote:
>> Under Aix directories have the mode 024xxxx instead of the customary
>> 04xxxx. Because of this when you sync a directory to or from an Aix
>> system it's never up to date.
>>
>> Here is a patch which fixes this. It causes rsync to look at
2002 Jul 31
1
rsync: omit summary with a single -v
It would be nice if there were a flag which would have rsync behave
like a single -v but which would skip the two line summary info. I do
a lot of cron-based transfers and I want to see what gets transferred
if anything does, but I'd like it to be entirely silent otherwise.
Here is a patch which makes a single -v behave this way. -vv causes it
to include the extra info.
diff -r -X
2004 Mar 05
2
Problem with --link-dest when syncing AIX to Linux
Hello,
i'm using rsync 2.6.0 for daily-syncing some remote AIX 5.2 machine to a
local linux (RH 7.3) with using the --link-dest option for saving space
on incremental backups.
Even if there are no changes on the AIX machine, all files are newly
transferred on every new sync.
My test scenario (actisi=remote aix machine, actisa=local linux machine):
=====> Initial rsync
[mma@actisa
2023 May 17
1
[PATCH] Add --omit-{device,special}-times options
Similar to --omit-{dir,link}-times:
--omit-device-times omit device files from --times
--omit-special-times omit sockets and fifos from --times
Also, fix corner case that allows --omit-dir-times to be ignored. See
unchanged_attrs() and recv_generator()'s call to try_dests_non().
Marc.
diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/generator.c devel-3.2.7/generator.c
---
2004 Sep 15
0
[Bug 1764] New: dry-run does not show changes in owner / group, permission, or timestamp
https://bugzilla.samba.org/show_bug.cgi?id=1764
Summary: dry-run does not show changes in owner / group,
permission, or timestamp
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2006 Mar 20
1
Rsync acl patch 1.113 compilation problems on cygwin
Hi,
Recently, there have been some fundamental achievements regarding
acl-support on the cygwin platform. I thought that it would be convenient to
offer an acl-patch enabled rsync as a part of the cwrsync package (a yet
another minimalist rsync on cygwin solution). I get some compilation errors.
What I did:
- Downloaded acl patch v1.113 from rsync site
- Run commands below In the rsync source
2005 Jul 07
1
rsync 2.6.6pre1 released (ALERT: info on zlib security flaw)
There has been some talk about a zlib security problem that could let
someone overflow the buffers in the zlib decompression code, potentially
allowing someone to craft an exploit to execute arbitrary code. Since
this is a decompression bug, this can only affect an rsync daemon if
it allows uploads with the --compress option enabled.
If you run a daemon that allows uploads, you may wish to add
2005 Jul 07
1
rsync 2.6.6pre1 released (ALERT: info on zlib security flaw)
There has been some talk about a zlib security problem that could let
someone overflow the buffers in the zlib decompression code, potentially
allowing someone to craft an exploit to execute arbitrary code. Since
this is a decompression bug, this can only affect an rsync daemon if
it allows uploads with the --compress option enabled.
If you run a daemon that allows uploads, you may wish to add
2004 May 06
2
rsync-2.6.2: NFS clients confused after an rsync
We use rsync to update an nfs server. After an update, we noticed that
a large number of clients didn't see the updated data.
It took me a while to be able to reliably reproduce this problem, but it
happens on old and new versions of rysnc. It also happens across all
the platforms we use here (sun/linux/netapp).
This shows the problem: [Note my home directory is NFS mounted]
2012 Jun 09
2
[patch] NFSv4/ZFS ACLs
This is a PoC patch for NFSv4/ZFS ACLs.
The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs
without requiring a new command line option
NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is
present a separate POSIX draft ACL will not be present and there are new
APIs
to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and
POSIX
ACLs in
2005 Jul 26
1
[patch] paranoid checksum checking
The attached patch provides an additional check for the checksumming
mode to ensure that a file that is actually written out to disk can be
read back and has the same MD4 sum as the file on at the originating
location.
Regards,
Nick.
-------------- next part --------------
*** rsync-2.6.6pre1/receiver.c 2005-04-14 02:42:13.000000000 +0100
--- rsync-new/receiver.c 2005-07-26
2008 Feb 15
4
Revised flags patch
Hi,
first of all, sorry for taking so long. Unfortunately, some other tasks
kept coming up. Anyway, attached is the version of the flags patch, that
is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9
release.
I've included the option name change from the repository, so the
option is now called --fileflags. Improved from the previously
distributed version is the
2007 Aug 07
2
`*deleting' itemize output misaligned
Wayne,
I noticed that rsync's "*deleting" itemize output needs two trailing
spaces now that the other itemize codes are 11 characters wide. See
the patch below.
Matt
-------------
Index: log.c
===================================================================
RCS file: /cvsroot/rsync/log.c,v
retrieving revision 1.179
diff -u -r1.179 log.c
--- log.c 10 Jul 2007 13:55:49
2005 Jun 24
1
[PATCH] Fix itemize test for objdir != srcdir builds
Hi.
The choice of 'config.h' for testing does not consider the possiblity of
objdir != srcdir builds. The small patch below replaces 'config.h'
with 'configure.in' in keeping with the 'config' name choice.
Art Haas
Index: testsuite/itemize.test
===================================================================
RCS file: /cvsroot/rsync/testsuite/itemize.test,v
2008 Apr 15
1
rsync-3.0.2 fails testsuite in itemize
HI,
rsync-3.0.2 with patches/acls.diff,patches/xattrs.diff,patches/slp.diff
fails (most of the time) in the itemize test:
----- itemize log follows
Testing for symlinks using 'test -h'
makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/foo
makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/bar/baz
cd+++++++++ ./
cd+++++++++ bar/
2010 Aug 15
1
DO NOT REPLY [Bug 7622] New: Factor out common logic from itemize and unchanged_attrs functions
https://bugzilla.samba.org/show_bug.cgi?id=7622
Summary: Factor out common logic from itemize and unchanged_attrs
functions
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned at samba.org
2014 Jul 05
1
duplicated --itemize-changes hangs since 3.1.1pre1
One of our rsync updates has been getting stuck at the download point.
It gets the incremental list, deletes stuff but when it tries to
download new/updated files it gets stuck and aborts after the timeout;
it doesn't even create the temporary. Experimentation shows that it
happens because the --itemize-changes option is repeated (on purpose);
putting it only once works normally. Apparently