All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin Pankaj <ashwin.pankaj@lsi.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: xenstore reboot/crash watch
Date: Tue, 3 Nov 2009 15:50:45 +0530	[thread overview]
Message-ID: <4AF003FD.4080902@lsi.com> (raw)

Hi,

I tried googling this one - but documentation on @releaseDomain key in 
xenstore seems scanty.

   1. If a client registers a watch for this key - does it get called
      every time a domain restarts / crashes ?
   2. Why can't xenstore-ls, xenstore-read et al "see" this key ?
   3. docs/misc/xenstore.txt has this to say - "WATCH                  
      <wpath>|<token>|?
              Adds a watch.
      <snip>

              <wpath> can be a <path> to watch or @<wspecial>.  In the
              latter case <wspecial> may have any syntax but it matches
              (according to the rules above) only the following special
              events which are invented by xenstored:
                  @introduceDomain    occurs on INTRODUCE
                  @releaseDomain      occurs on any domain crash or
                                      shutdown, and also on RELEASE
                                      and domain destruction

              When a watch is first set up it is triggered once straight
              away, with <path> equal to <wpath>.  Watches may be triggered
              spuriously.  The tx_id in a WATCH request is ignored."
        So would the following python code register watch for  restart
      events of ANY domain - 'watch = xswatch("@releaseDomain",
      watch_func, xshandle())' ?

- Regards,
Ashwin

             reply	other threads:[~2009-11-03 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 10:20 Ashwin Pankaj [this message]
2009-11-04 11:12 ` xenstore reboot/crash watch Vincent Hanquez

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=4AF003FD.4080902@lsi.com \
    --to=ashwin.pankaj@lsi.com \
    --cc=xen-devel@lists.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.