When preserve_perms is not set, rsync sets a default permission based on
the original permissions and the umask. A comment in flist.c says that is
what GNU cp does, so that's why rsync does it. Comments in generator.c
and receiver.c indicate that if a file already exists and preserve_perms
First, you should know that rsyncing a .gz file is not very worthwhile
because the rsync algorithm does not do a good job of efficiently
transferring them, unless you've got a modified gzip that adds a
--rsyncable option and you used the option. The patch is in the 2.5.5
source
On Mon, Dec 23, 2002 at 11:42:07PM -0800, Jos Backus wrote:
On Mon, Dec 23, 2002 at 02:13:51PM -0800, Stephen Friedl wrote:
The change in popt/popt.c is to work around a bug in the SCO UNIXWare 8
compiler: it doesn't properly deal with alloca() being called from the
middle of another
On Tue, Dec 24, 2002 at 07:26:38AM -0600, Dave Dykstra wrote:
On Mon, Dec 23, 2002 at 11:42:07PM -0800, Jos Backus wrote:
On Mon, Dec 23, 2002 at 02:13:51PM -0800, Stephen Friedl wrote:
The change in popt/popt.c is to work around a bug in the SCO UNIXWare 8
compiler: it doesn't properly
I have 2 cron jobs on machine A that do the following: copies a
directory tree to another disk on the same machine and also copies to
a remote machine i.e.
0 * * * * rsync -az -delete /disk1/dir/ /disk2/dir
0 * * * * rsync -az -delete /disk1/dir/ machine2:/disk2/dir
This is workig fine, but
If the UNIXWare compiler
can't handle the construct Stephen could forward the patch
to the libpopt project and file a bug report with SCO.
I have filed a bug report with SCO (with detail at the assembler level
to help them track it down), and I'll look into the libpopt integration
as well.
I
