From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 1 of 3] xencommons: Kill xenstored when stopping xencommons Date: Mon, 28 Jun 2010 15:01:04 +0100 Message-ID: <1277733664.31214.88.camel@zakaz.uk.xensource.com> References: <1277730769.31214.48.camel@zakaz.uk.xensource.com> <4C28A8DB.5060506@eu.citrix.com> <1277732921.31214.69.camel@zakaz.uk.xensource.com> <4C28AA00.4020209@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C28AA00.4020209@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: George Dunlap , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, 2010-06-28 at 14:56 +0100, Vincent Hanquez wrote: > > > > 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. Wow, it's like living in the future! Was the intention that users only ever use a "restart" target (assuming it passes --restart) in the initscript rather than the stop->start pair some people are used to? Even if stop does a clean shutdown unless start uses --restart we have the same issue with forgetting watches etc. Do we need a separate start-like target which reads the db (for use after you've done a stop) or is it safe to use --restart by default? Can an initscript distinguish a start at start of day from a start run by the user (following an earlier stop) and hence add the --restart automagically? Ian.