On Fri, May 23, 2008 at 11:23:24AM -0500, Michael Short wrote:
> Would it be possible to analyze and store hashing information about
> file A before it is neccessary to compare it with file B? I want to
> know because in my software file A will not be available to either
> system when the new versi
Hi larry,
This rsync was compiled on an intel running 10.4.11 so the
architecture is right. I am wondering though if it would make a
difference to compile it on the 10.5.2 machine it seems to hang on
I have assumed all along that compiling it on the previous OS would be
upward compati
Hello,
Would it be possible to analyze and store hashing information about
file A before it is neccessary to compare it with file B? I want to
know because in my software file A will not be available to either
system when the new version of the file must be sent.
Sincerely,
--
Michael Short
Secu
Robert,
Perhaps unrelated, but I had a hang-at-end situation which at least
sounds similar. I tried to use a 3.0.x binary which had been compiled
on a PPC, on an intel-mini; it seemed to hang at the end.
Recompiled on the intel-mini, no problem since then.
Larry
--
At 9:57 PM -0400 5/2
On 23 May, 2008, at 03:31 , Jeff Waddell wrote:
I only have one rsync version (3.0.3 pre2) on the Solaris target. I
ran a
--version on both systems, and noticed that the Solaris version
reports the
following capabilities: "ACLs, no xattrs, no symtimes, no file-
flags" where
the Mac reports
Hi All,
My wrapper application for rsync 3.0.2 on osx has been working
smoothly except for reports of it hanging on the last file of the
transfer to a local firewire drive. We seem to have solved the mystery
of the slow transfers but now, every four or five runs, it hangs at
the last fi
I worked out what the problem was in the first place.
I just had to make list_only and read_only equal to zero.
thanx anyways,
zahed
--
View this message in context:
http://www.nabble.com/errors-while-renaming-files-tp17399191p17420694.html
Sent from the Samba - rsync mailing list archive at
