similar to: rsync hang at end

Tiger's rsync anomalies I'm trying to sort out some anomalies using rsync locally. Booted to Volumes/LaCie_Disk_A I create a full direct clone with: sudo asr -erase -source /Volumes/Mirrored_HD_Set -target /Volumes/LaCie_Disk_B then boot to it and check it out. Then booted back to Mirrored_HD_Set I do a little other work (i.e. some files are changed). Then for a differential

Hello All, I have lately heard from a couple of people that delete option was not deleting extraneous files on destination. This only happens when there are several source directories and at destination some show delete working and others not. I can not reproduce the issue so it is hard to pinpoint. one example: This is on OSX Mavericks running rsync 3.0.9 with the usual osx patches and

Dear All, I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options. This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created. -aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup

Hi All, I have been getting reports from users of backuplist+, my wrapper application for rsync (currently with build of 3.0.6), about odd behavior after updating to OS 10.6 Snow Leopard. Basically: the problem occurs backing up a directory to a local mounted network volume. Previously all worked fine but after updating to 10.6 there are reports that no files get copied and the destination fills

Hi All, I am have been cloning drives with several versions of xcode and am seeing very long copy times. Perhaps just because of xcode I am noticing the change. Xcode of course has many files (400,000+) many xattrs and compressed bits, decmpfs… so only natural it will be slow but sometimes upwards of 1/2 hour to a fast drive for xcode. If I turn off Xattrs (leave out the X) it flies through in

Dear All, I found a workaround for the corrupted backup app package files though there is probably a more intelligent way. When the destination is empty or missing (rather than an update) rsync.c calls make_backup and returns 1 when it encounters if (x_lstat(fname, &sx.st, NULL) < 0) return 1; the calling code in rsync.c: if ( make_backups > 0 && overwriting_basis) {

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

Hello, I'm new on this list, here's the problem we are experiencing : We have installed pware61-64.samba.3.6.0.0.bff.gz on an Aix partition running on 6100-06-05-1115. We have succeeded in entering the system in our AD. We can reach the domain : commands /opt/pware/bin/wbinfo -a USERNAME is correct. The problem is that lsuser -R WINBIND don't work : message "User does not

Am 15.09.2015 um 19:09 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, Leon Fauster <leonfauster at googlemail.com> wrote: >>> On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> this also helps to boot >> >> http://www.rodsbooks.com/refind/ > > rEFInd will work on EFI-based Macs, but not on old PPC

Is this even a possibility? Both my brother and I have PPC G3 Mac's that we would like to install Linux on. I have downloaded a couple of Debian ISOs and a couple of Gentoo ISOs. All four would easily fit on a single CD. So, my question/problem is, is it possible to configure a menu to chose between them, that will boot up on a Mac PPC? Thanks, Lonnie -- Later, Lonnie Mostly Debian,

Dear R Users I have two questions about how R makes use of memory on a Windows computer. On my machine certain R jobs seem to stop with messages such as... "Error: cannot allocate vector of size 215.0 Mb" ...when, according to Windows Task Manager, there are still hundreds of megabytes of physical memory available. These jobs usually stop when the peak commit charge is around 2.6GB (in

https://bugzilla.samba.org/show_bug.cgi?id=1476 abartlet@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abartlet@samba.org Status|RESOLVED |REOPENED Resolution|WORKSFORME | -------

Returning to this list after a long hiatus: rsync 3 has been working very well for me for many years, as a supplementary backup tool for MacOSX. However, attempting to build the new 3.1.0 release on a brand new Mountain Lion box with my standard 'fileflags' and 'crimes' patches applied, make fails, reporting that 'force_change' is undeclared. In fact, the problem occurs

https://bugzilla.samba.org/show_bug.cgi?id=8019 Summary: Various improvements to the fileflags patch Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mike at bombich.com

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

Hi All, I just tried (on OS10.5.2) the new fileflags.diff patch patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff (see result below- I fixed the rej's ) then ./configure make then tried it out but it isn't copying the creation dates now.... just wondering if I missed something .. Rob D robert-dutoits-powerbook-g4-15:rsync-3.0.0pre10 astrid$ patch -p1

Looking at http://rsync.samba.org/ftp/rsync/patches/fileflags.diff -- It looks like the changes from fileflags-fixes.diff patch were applied to the patch from http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz , but this entire chunk of the that original diff file was lost: > diff -up a/config.h.in b/config.h.in > --- a/config.h.in > +++ b/config.h.in > @@ -64,6 +64,9 @@

Good day, I am having trouble compiling rsync 3.0.6 on Red hat Linux EL 5.3. I have downloaded 3.0.6, and the patches for 3.0.6. I then do the following: $ patch -p1 <patches/fileflags.diff $ ./prepare-source $ ./configure ?disable-acl-support $ make When I run ./rsync, the following is returned: Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long

I have an rsync daemon running on a FreeBSD 7.3 system. It is running rsync 3.0.4 with fileflags enabled. I have the following six files on it which are all hardlinks and have the immutable flag set: 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chfn 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chpass 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005

Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -------------------------------------------------------------- #! /bin/sh # # set -x DIR="/var/tmp/rsync_$(date +%s)/" mkdir "${DIR}/" # Preparing dir_A mkdir