From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Subject: Re: [PATCH 1 of 3] xencommons: Kill xenstored when
	stopping xencommons
Date: Mon, 28 Jun 2010 14:56:16 +0100
Message-ID: <4C28AA00.4020209@eu.citrix.com>
References: <patchbomb.1277729923@gdunlap-desktop>	
	<e71645625934f162c3d7.1277729924@gdunlap-desktop>	
	<1277730769.31214.48.camel@zakaz.uk.xensource.com>	
	<4C28A8DB.5060506@eu.citrix.com>
	<1277732921.31214.69.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1277732921.31214.69.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/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/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: 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>
List-Id: xen-devel@lists.xenproject.org

>
> 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