From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <Xen-devel@lists.xensource.com>
Subject: Re: Xenbus watch firing over and over
Date: Thu, 04 Jan 2007 13:18:32 +0100 [thread overview]
Message-ID: <1167913112.2883.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20070103182539.GA26642@leeni.uk.xensource.com>
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
next prev parent reply other threads:[~2007-01-04 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 18:16 Xenbus watch firing over and over Jacob Gorm Hansen
2007-01-03 18:25 ` Ewan Mellor
2007-01-04 12:18 ` Jacob Gorm Hansen [this message]
2007-01-04 12:28 ` Ewan Mellor
2007-01-05 11:21 ` Grzegorz Milos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1167913112.2883.2.camel@localhost.localdomain \
--to=jacobg@diku.dk \
--cc=Xen-devel@lists.xensource.com \
--cc=ewan@xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.