|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-tools] [RFC] Daemon startup order
Hi,
A few people are having problems with the new console daemon and I've
tracked the problem down to the order in which daemons are started.
Here's what currently happens:
1) xend (the script in tools/misc) start will launch xcs and consoled
2) xend (the python server) will launch xenstored whenever it needs it
This creates a bit of a chicken and the egg problem since consoled needs
xenstored to function. There's a few options:
1) Have consoled (and all future daemons) implement the logic to wait
for xenstored to start
2) Move xenstored launching to xend (the script in tools/misc)
3) Give all the daemons proper init.d scripts with dependencies
I'm partial to #3 although #2 would be a fine quick hack.
For now, if anyone gets messages about not being able to read the tty
with xm console, simply run consoled.
Regards,
Anthony Liguori
_______________________________________________
Xen-tools mailing list
Xen-tools@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-tools
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-tools] [RFC] Daemon startup order,
Anthony Liguori <=
|
|
|
|
|