Re: [Xen-devel] [PATCH 2 of 2] xencommons: Wait for xenstored to start before setting dom0 name

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2010-06-29 at 15:37 +0100, Jeremy Fitzhardinge wrote:
> 
> 
> Why isn't xenstored ready by the time the main process exits?  Seems
> like a bug in xenstored. Does oxenstored get this right? 

Looks like Bastian tried to fix this in C xenstored years ago with:
        changeset:   17296:21d9575c669e
        user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
        date:        Wed Mar 26 13:21:42 2008 +0000
        files:       tools/misc/xend tools/xenstore/xenstored_core.c
        description:
        xenstored: Delay forking until after listening sockets are
        opened. Also, in startup xend script, delay further startup until
        xenstored initial child process has exited. This serialises xenstored
        startup with that of other daemons (e.g., xenconsoled).
        
        Signed-off-by: Bastian Blank <waldi@xxxxxxxxxx>
But it was reverted shortly after:
        changeset:   17304:ed67f68ae2a7
        user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
        date:        Thu Mar 27 09:12:09 2008 +0000
        files:       tools/misc/xend tools/xenstore/xenstored_core.c
        description:
        Revert 17296:21d9575c669e.
        Signed-off-by: Keir Fraser <keir.fraser@xxxxxxxxxx>
because it broke something. The thread at
http://lists.xensource.com/archives/html/xen-devel/2008-03/msg00758.html
has more details.

I'm not especially inclined to fix the C xenstored, lets hasten the
switch to oxenstored instead.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel