All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian.Limpach@cl.cam.ac.uk
Cc: Arun Sharma <arun.sharma@intel.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Timeout connecting to device
Date: Thu, 25 Aug 2005 13:18:56 +1000	[thread overview]
Message-ID: <1124939936.9810.16.camel@localhost.localdomain> (raw)
In-Reply-To: <3d8eece2050824012547b9bb89@mail.gmail.com>

On Wed, 2005-08-24 at 09:25 +0100, Christian Limpach wrote:
> On 8/24/05, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > The trace file is actually better in my experience.  Also look for
> > "error" nodes in the store (although Christian removed some of those
> > paths in the merge).
> 
> I only removed the ones which were not fatal because I was under the
> impression initally that adding an error node does indicate a final
> error after which it would be up to a control tool to sort out the
> failure or report it.

Well, I expect there to be an error node at some point in the normal
case: you look in the backend and something isn't there yet, you want to
indicate that, because it may never change (in the normal case, it will
appear soon and we will delete the error node).

The error node idea might be overly simplistic: its non-existence
doesn't tell you the device is ok (it might have just been created).
Makes it harder to synchronously create a device.

Will think more on this...
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

  reply	other threads:[~2005-08-25  3:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 20:41 Timeout connecting to device Arun Sharma
2005-08-22 20:42 ` Arun Sharma
2005-08-24  1:36 ` Arun Sharma
2005-08-24  4:43   ` Rusty Russell
2005-08-24  8:25     ` Christian Limpach
2005-08-25  3:18       ` Rusty Russell [this message]
2005-08-25 11:01         ` Christian Limpach
2005-08-26  0:27           ` Rusty Russell
2005-08-26 10:37             ` Christian Limpach
2005-08-29  0:17               ` Rusty Russell
2005-08-29  0:23                 ` Christian Limpach
2005-08-25  0:31     ` Arun Sharma

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=1124939936.9810.16.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=arun.sharma@intel.com \
    --cc=xen-devel@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.