Hi, thanks for the patch and comments on rsync3. I'm in the process
of committing these patches to the 2.6.0 branch.
I want to get a stable 2.5 out to give people some relief for the
recent burst of fixes, and I think in this case it's probably better
to live with the devil we know.
***
Thanks, this will be merged in 2.6. Please let me know if anything
further is required.
--
Martin
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Oh, no. It's a pretty normal commandline. It was needed, however, to
show the sorts of things that can be wrong. From your syntax, You are
contacting a rsyncd on mymachine. From this, I assume you have built an
rsyncd.conf file, and either put it in /etc or told rsync where to find
it,
Greetings,
We found out today that rsync has been missing some files. Here
is the senerio:
We have two nfs servers in different datacenters, one being the
backup to the other. We want to keep them up to date so we use rsync
inside crontabs. We have Solaris, AIX, True64
On 26 Mar 2002, Paul LaMadeleine [EMAIL PROTECTED] wrote:
I think I can get away with specifing the --checksum flag, but
I'm just not sure.
Yes, I think that is the best solution. It will of course be pretty
slow since rsync will have to read every file on the filesystem every
time,
Hello,
May be I am wrong, but why rsync tells me that it's
nothing to do?
I just want to synchronizethe directory's
attributes(with no recursion) such as:
permissions, owner, group
andtime.
Example:
===
host1# pwd
/var/rsync/host2
!
! At first, I copy only subdirecory
On 26 Mar 2002, Greg A. Woods [EMAIL PROTECTED] wrote:
I want to get a stable 2.5 out to give people some relief for the
recent burst of fixes, and I think in this case it's probably better
to live with the devil we know.
Well, I don't know about that -- the main reason for my fix is
[ On Wednesday, March 27, 2002 at 15:39:32 (+1100), Martin Pool wrote: ]
Subject: Re: fixes for bugs in error handling in rsync-2.5.2; and updates for
rsync3.txt
I had a look at this again today and it looks OK.
Do you have a reproducible case similar to the bug you experienced?
Not at
