Date: Mon, 10 Nov 2003 09:54:32 -0800 (PST)
From: Davide Libenzi <davidel@xmailserver.org>
To: Andrea Arcangeli <andrea@suse.de>
cc: Larry McVoy <lm@bitmover.com>, "H. Peter Anvin" <hpa@zytor.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel.bkbits.net off the air
In-Reply-To: <20031110165738.GD6834@x30.random>
Message-ID: <Pine.LNX.4.44.0311100952280.2097-100000@bigblue.dev.mdolabs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1077
Lines: 28

On Mon, 10 Nov 2003, Andrea Arcangeli wrote:

> the updates shows up on kernel.org, rsync can't even hang on per-file
> locks, sure it can't be coherent as a whole.
> 
> The best way to fix this isn't to add locking to rsync, but to add two
> files inside or outside the tree, each one is a sequence number, so you
> fetch file1 first, then you rsync and you fetch file2, then you compare
> them. If they're the same, your rsync copy is coherent. It's the same
> locking we introduced with vgettimeofday.
> 
> Ideally rsync could learn to check the sequence numbers by itself but I
> don't mind a bit of scripting outside of rsync.

Wouldn't a simpler  "stop-rsync -> update-root -> start-rsync" work? If 
you'll hit an update you will get a error from your local rsync, that will 
let you know to retry the operation.


- Davide


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/