[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xend stop fails to call network-script stop

  • To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.