From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: [RFC] Daemon startup order Date: Thu, 04 Aug 2005 10:46:24 -0500 Message-ID: <42F23850.8020704@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-tools@lists.xensource.com, xen-devel List-Id: xen-devel@lists.xenproject.org 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