Date: Tue, 11 Nov 2003 16:02:42 +0100
From: Andrea Arcangeli <andrea@suse.de>
To: walt <wa1ter@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel.bkbits.net off the air
Message-ID: <20031111150242.GE1649@x30.random>
References: <fa.na6uip6.p2erhm@ifi.uio.no> <fa.dbkbts9.1k7ohhd@ifi.uio.no> <3FB05EDE.6090007@myrealbox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FB05EDE.6090007@myrealbox.com>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 980
Lines: 21

On Mon, Nov 10, 2003 at 08:00:30PM -0800, walt wrote:
> Andrea Arcangeli wrote:
> 
> >>On Mon, 10 Nov 2003, Andrea Arcangeli wrote:
> >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...
> 
> How is this different from writing one file named LOCK while updating
> the tree?

it's very different, your file named LOCK can be created and deleted
while rsync was running, and rsync will never notice. rsync is readonly,
it'll never care about locks.
-
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/