All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-tools@lists.xensource.com, xen-devel <xen-devel@lists.xensource.com>
Subject: [RFC] Daemon startup order
Date: Thu, 04 Aug 2005 10:46:24 -0500	[thread overview]
Message-ID: <42F23850.8020704@us.ibm.com> (raw)

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

                 reply	other threads:[~2005-08-04 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F23850.8020704@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-tools@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.