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-users

Re: [Xen-users] RE: xend stop doesn't call network-script stop

To: Schober Walter <Walter.Schober@xxxxxxxxx>
Subject: Re: [Xen-users] RE: xend stop doesn't call network-script stop
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 15 May 2007 14:58:58 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 May 2007 06:57:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <30FA315AB19B5F49B7B7C5CA912B081104F625@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <30FA315AB19B5F49B7B7C5CA912B081104F625@xxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, May 15, 2007 at 03:51:03PM +0200, Schober Walter wrote:
> Attached my network-bridge-bonding script, if helpful for someone. 
>  
> Is it normal, that 
> root      5450     1  0 03:12 ?        00:00:00 python /usr/sbin/xend
> start
> root      5453  5450  0 03:12 ?        00:00:00 python /usr/sbin/xend
> start
> stays running that way?

Yes, the parent process is a 'guardian angel' so to speak, while the
second is the actual XenD server. The former will restart the latter
if it crashes. 

> Any other hint, why 'service xend stop' doens't call the script?
>  
> I'm about to believe, that this isn't really interesting thus no one
> really cares about to get the "stop" working, too.
> My scripts work perfectly, if called in the shell.

Having  'service xend start' futz around with networking is (reasonably)
safe because at the time you boot most apps[1] won't be using networking
so their connectivity won't be disrupted. If you call 'service xend start'
multiple times the subsequent times will be no-op.  If 'service xend stop'
were to call network-bridge to shutdown networking then this would cause
serious disruption to any apps using networking at the time.

To be honest, XenD has no business touching networking what-so-ever.
Even at boot time, this will totally hose your system if you are booting
of iSCSI or NFS root. Longer term, I'd like to see Xend's network-script 
going  away completely & with the setup  being left to the regular distro
provided networking scripts which are already capable of setting up far more
complex & interesting configurations in a safer manner.

Regards,
Dan.

[1] iSCSI / NFS boot being the counter-examples
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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