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] xend stop fails to call network-script stop

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xend stop fails to call network-script stop
From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
Date: Fri, 7 Oct 2005 14:49:06 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 07 Oct 2005 13:46:34 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=emnA7NKXAHUWggjSbnY2nbqQ2NfF6bCHQoap/5jjK/duU7Regyk4dF6V6rOyNDVBRAtsQOts51mye96v5Esl+MaEr8Z9j0OLMHW/z/IPd6wMO67YcHEKxyM1lpD3ptbi0F5MKMRt2Zcju3/5oJFHJOd8z5nB8116WanBTheYJr8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5d482e3bb1b2bc020a8e880d318917ef@xxxxxxxxxxxx>
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: <623652d50510070550j3ab2517r@xxxxxxxxxxxxxx> <5d482e3bb1b2bc020a8e880d318917ef@xxxxxxxxxxxx>
Reply-to: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 07/10/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>
> On 7 Oct 2005, at 13:50, Chris Bainbridge wrote:
>
> > Hi, possible bug, wondering if anyone else can confirm this?
>
> Currently it's a 'feature'. If you restart xend then changing network
> configuration twice may introduce needless network races. In most/all
> cases it will be harmless to leave the network in xend-running
> configuration.

Maybe you could make this behaviour optional in xend config?

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

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