From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Thunes Subject: Re: Network scripts start/stop Date: Sat, 05 Apr 2008 12:00:57 -0400 Message-ID: <47F7A239.4010008@brewtab.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Alright, thanks - Chris Thunes Keir Fraser wrote: > On 5/4/08 00:28, "Christopher Thunes" wrote: > > I was poking around with some network scripts for Xen today > (3.2-testing) and noticed that regardless of whether xend start, > xend restart, or xend stop was called a 'start' argument was passed > on to the network script (network-bridge, network-route, etc.). I > can't imagine this is normal behavior and it seems that the only > place that these scripts are called is from a global function call > in xend/XendPIF.py around line 35 ("Vifctl.network('start')"). I > commented this line out and added appropriate calls to > Vifctl.network('start') and Vifctl.network('stop') in > xend/server/SrvServer.py in the functions cleanup and start. If > someone can let me know if this is standard behavior and if not, if > there is a better way to fix the problem it would be much appreciated. > > > The established behaviour is that networking is brought up with xend, > and remains up even across xend stops and restarts. Possibly xend stop > and restart should not be calling the network scripts at all, but that’s > a pretty minor issue. > > -- Keir