From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 3] xencommons: Kill xenstored when stopping xencommons
Date: Mon, 28 Jun 2010 14:56:16 +0100 [thread overview]
Message-ID: <4C28AA00.4020209@eu.citrix.com> (raw)
In-Reply-To: <1277732921.31214.69.camel@zakaz.uk.xensource.com>
>
> It's not so much the stopping per se but more the starting it again and
> expecting the system to work. Can oxenstored cope with that? Where does
> it persist its watches to?
>
>
yes, it does keep the watches (along with anything else required) in its
database which it's supposed to dump when beeing kill nicely and using
--restart so that it read the database at startup.
--
Vincent
next prev parent reply other threads:[~2010-06-28 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 12:58 [PATCH 0 of 3] xencommons init script improvements George Dunlap
2010-06-28 12:58 ` [PATCH 1 of 3] xencommons: Kill xenstored when stopping xencommons George Dunlap
2010-06-28 13:08 ` Stefano Stabellini
2010-06-28 13:10 ` George Dunlap
2010-06-28 13:23 ` Ian Campbell
2010-06-28 13:12 ` Ian Campbell
2010-06-28 13:51 ` Vincent Hanquez
2010-06-28 13:48 ` Ian Campbell
2010-06-28 13:56 ` Vincent Hanquez [this message]
2010-06-28 14:01 ` Ian Campbell
2010-06-28 14:23 ` Vincent Hanquez
2010-06-28 13:50 ` Keir Fraser
2010-06-28 14:16 ` Vincent Hanquez
2010-06-28 12:58 ` [PATCH 2 of 3] xencommons: Make init script more verbose George Dunlap
2010-06-28 16:09 ` Ian Jackson
2010-06-28 16:30 ` George Dunlap
2010-06-28 12:58 ` [PATCH 3 of 3] xencommons: Wait for xenstored to start before setting dom0 name George Dunlap
2010-06-28 16:01 ` Ian Jackson
2010-06-28 16:18 ` George Dunlap
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=4C28AA00.4020209@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.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.