All of lore.kernel.org
 help / color / mirror / Atom feed
From: aq <aquynh@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Li, Xin B" <xin.b.li@intel.com>,
	xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
	David F Barrera <dfbp@us.ibm.com>, Li Ge <lge@us.ibm.com>,
	xen-devel-bounces@lists.xensource.com
Subject: Re: console problem
Date: Sat, 6 Aug 2005 14:37:41 +0900	[thread overview]
Message-ID: <9cde8bff0508052237798c45d3@mail.gmail.com> (raw)
In-Reply-To: <42F3CE4A.4080605@us.ibm.com>

On 8/6/05, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Yes, I'm aware of this.  The problem is that we've never had a good
> dependency system for the daemons we started.  The extra daemon has made
> the problem much worse and now we're seeing timing issues.
> 
> You can work around the problem by manually starting consoled (you may
> have to restart xenstored too).  Under the right circumstances, xend
> restart will loop because xenstored gets itself hosed.
> 
> I'm reworking a lot of this code right now to make it more robust and
> solve the problem completely.  Just hang in there a bit :-)

as you are rewriting consoled, how about renaming it (for ex, to xenconsoled) ? 

now we have xenblkd, xend, xenstored, so if all the xen-related
processes have xen as prefix (which is a good thing), we can see what
is running by just one command "ps|grep xen" :-)


regards,
aq

  reply	other threads:[~2005-08-06  5:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  5:43 console problem Li, Xin B
2005-08-05 15:34 ` Li Ge
2005-08-05 16:34   ` Keir Fraser
2005-08-05 20:35   ` David F Barrera
2005-08-05 20:38     ` Anthony Liguori
2005-08-06  5:37       ` aq [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 16:23 Stas Sergeev
2005-09-15  6:39 ` UNIREA Sannicolau Mare
2005-09-28  2:24   ` Clarence Dang
2005-09-02 20:53 Alain
2005-08-31  5:23 UNIREA Sannicolau Mare
2005-08-31 22:06 ` Justin Zygmont
2005-09-01 10:45   ` UNIREA Sannicolau Mare
2005-09-02  3:05     ` Justin Zygmont
2005-09-05  5:19       ` UNIREA Sannicolau Mare
2005-09-05 23:19         ` Justin Zygmont
2005-09-14  5:12           ` UNIREA Sannicolau Mare
2005-09-02 10:54 ` Andrzej Kaczmarczyk
2005-08-06  5:45 Li, Xin B
2005-08-06  9:39 ` Keir Fraser
2005-08-06 18:47   ` Anthony Liguori
2005-08-05  5:04 Li, Xin B
2005-08-05  5:40 ` Anthony Liguori
2005-08-05  3:48 Li, Xin B
2005-08-05  3:52 ` Anthony Liguori
2005-08-05  2:23 Stefan Berger
2005-08-05  2:30 ` Anthony Liguori
2005-08-05  3:14   ` Stefan Berger
2005-06-10 22:05 Console problem Monica Correa
2005-06-10 22:25 ` Magenheimer, Dan (HP Labs Fort Collins)
     [not found] <5.1.0.14.0.20020719083530.00a11d50@raven-villages.net>
     [not found] ` <200207211506.57760.ADharankar@ATTBI.Com>
2002-07-23 19:13   ` console problem Mark Chambers
2002-07-26  1:00     ` Arun Dharankar
2002-03-05  9:18 Console problem Andre.Messerschmidt
2002-03-05 19:29 ` James Simmons

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=9cde8bff0508052237798c45d3@mail.gmail.com \
    --to=aquynh@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=dfbp@us.ibm.com \
    --cc=lge@us.ibm.com \
    --cc=stefanb@us.ibm.com \
    --cc=xen-devel-bounces@lists.xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xin.b.li@intel.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.