From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jacob Gorm Hansen <jacobg@diku.dk>
Subject: Re: Xenbus watch firing over and over
Date: Thu, 04 Jan 2007 13:18:32 +0100
Message-ID: <1167913112.2883.2.camel@localhost.localdomain>
References: <1167848163.2591.5.camel@localhost.localdomain>
	<20070103182539.GA26642@leeni.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20070103182539.GA26642@leeni.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <Xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2007-01-03 at 18:25 +0000, Ewan Mellor wrote:

> As far as xenstored is concerned, someone is explicitly deleting and
> reregistering that watch -- I don't think this is a bug in xenstored.
> You
> should expect to receive a watch event as soon as a watch is
> registered -- it
> looks to me like someone is receiving that event, then unwatching the
> node,
> reading its value, and reregistering the watch.

That explains it, I was trying a simple single-threaded setup where the
watch is unregistered once it has fired. What is the rationale for
triggering the watch on registration?

Jacob