This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 1 of 3] xencommons: Kill xenstored when stopping

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?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>