Re: [Xen-devel] Xenbus watch firing over and over

[Jacob Gorm Hansen <jacobg@xxxxxxx>]

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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel