WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xenbus problems solved (soft of)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xenbus problems solved (soft of)
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 6 Oct 2005 18:16:10 +0100
Delivery-date: Thu, 06 Oct 2005 17:13:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e08041f30510060341p728efb57nc6ed85ea96f7d937@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e08041f30510060341p728efb57nc6ed85ea96f7d937@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Oct 06, 2005 at 12:41:21PM +0200, Jacob Gorm Hansen wrote:

> Another thing that I discovered is that the use of xenstore for error
> messages is problematic. The backend will typically have a watch on
> the node it is logging the error message to, causing infinite watch
> trigger -> log error -> watch trigger loops.

I agree that this is problematic.  I have assigned it bug #286.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>