Hi:
I really want to know how rsync works.
Once it synchronize a file. Does rscync first create a temporary in the
remote machine first and then rename it? Or it direct write the difference
into the dest-file?
Could you please tell me what will happen to the dest-file when a rsync
process interru
On Mon, May 17, 2004 at 05:18:10PM -0400, Chris Shoemaker wrote:
> BTW, there is a work-around. If you don't mind duplicating the mirror
> twice, one solution is to do a regular (no --write-batch) rsync update of one
> copy of the mirror, and then do the --write-batch during a local to local
On Mon, May 17, 2004 at 05:18:10PM -0400, Chris Shoemaker wrote:
> The "knowledge" or "memory" of that exact state is more likely to
> reside with the receiver (who just left that state) than with the
> sender (who may never have been in that state). Therefore it is more
> likely to be useful to t
On Mon, May 17, 2004 at 10:15:23AM -0400, Alberto Accomazzi wrote:
>
> Chris,
>
> to put things in the right prespective, you should read (if you haven't
> done so already) the original paper describing the design behind batch
> mode. The design and implementation of this functionality goes ba
On Mon, May 17, 2004 at 09:22:14AM -0700, Wayne Davison wrote:
> On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> > #0 0x400a46d9 in strncmp () from /lib/libc.so.6
>
> That looks like the segfault I fixed [that affected] 2.6.1.
No, that's not right. I'm mis-remembering when that c
I've never seen this one before. I'm using rsync 2.6.2 on both ends.
Server (Athlon, 768MB RAM) checks out just fine. The only anomoly appears
to be that this process has been running for 248268.43 seconds (this is
not unexpected with this particular host we're backing up).
Commandline:
/usr
Andreas Ley wrote:
I haven't been able to duplicate the crash you two are seeing, so if
either of you can send me a backtrace of the crash (either from a core
dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in str
Hi everybody,
I use RSYNC under windows (cygwin) on both server and client side for syncing 2 big
directories over an VPN IPSEC links.(1 GB of data for around 30 000 files). The sync
shows these kind of errors for some clients. Here is the command that I use in a batch
file to syncing the fold
On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> #0 0x400a46d9 in strncmp () from /lib/libc.so.6
That looks like the segfault I fixed in 2.6.1. I looked back at your
original message, and it looks like I misread ">= 2.6.1" as "> 2.6.1".
If you're using 2.6.1, please upgrade to 2.6.
Hi all,
I'm wondering if the following is rsync-related or an issue with my
supposedly synchronous internet connection:
I have a server running an rsync daemon. When I simultaneously pull and
push files to this server using two separate processes on the client
(different directories), I get abo
>I haven't been able to duplicate the crash you two are seeing, so if
>either of you can send me a backtrace of the crash (either from a core
>dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in strncmp () from /l
Chris,
to put things in the right prespective, you should read (if you haven't
done so already) the original paper describing the design behind batch
mode. The design and implementation of this functionality goes back to
a project called the Internet2 Distributed Storage Infrastructure
(I2-DSI
12 matches
Mail list logo
