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/
Home Products Support Community News


Re: [Xen-users] Re: Getting one Dom U Guest to wait to startup until an

To: Jason Brooks <jason@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: Getting one Dom U Guest to wait to startup until another one's done starting up?
From: Bob Linkonij <boblnknj0@xxxxxxxxx>
Date: Tue, 12 May 2009 12:50:52 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 May 2009 12:51:37 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=54grtRkEJIYwH1KyeMCHQGDCvg0V+xucxxFesqaGbg4=; b=uI6+QhzfLyS4KHa2yVYp0Hf1K5kbRvoMHhIl6IDeQgiWg8QmATQ9mOjZ98JZMenumZ zE1OHUMhYxSt76OWl10Is75hs6O5A6+bngfK5gOY82WcCJJgTLYzt9OhF0yptFTe7KVV 6r3N+yAyjk8fyet7CTFSSaMRfZODLyWpSRngQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SfrxwLhi5n07c8axZy6Q5oW0v91T0PmVMJqlvakRaBg6Z0N3b6nX8xtAtfajCNluxk SAD6Ngfbu3QgDBiSOe/e416vvULQ0DCjmzlx2DPg0P33npIv/lP58BVygEZLJYiAnUpz BiSaS13TI5DAXcynhmvivq4VFAuJGQvPTepCY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6706C39A-6FE2-43E7-9789-202FC8C2AF36@xxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <54f972110905081430n4cf90e0dse70ce17f3ccece59@xxxxxxxxxxxxxx> <54f972110905121224g738aded8o9df7224d51c284a1@xxxxxxxxxxxxxx> <6706C39A-6FE2-43E7-9789-202FC8C2AF36@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey Jason,

On Tue, May 12, 2009 at 12:31 PM, Jason Brooks <jason@xxxxxxxxxxxxxxx> wrote:
> Hello,
> I can think of an item: it's the same as if you have separate servers with
> dependencies:
> create another rc script that runs after the network startup.  have it use
> nmap, or something to ping the other system periodically and wait until the
> correct service(s) are up.  then exit.
> Assuming you are running runlevel 3, create a link in /etc/rc3.d/ called
> S<xx>Wait that points to this script.  change the <xx> part to be certain it
> runs after the networking script, but before the next script.

I never used nmap, but I guess I can figure it out. That's a good
idea.  THanks a lot.

I'm kindof surprised that Xen doesn't have a "start this after that is
up" function, because it does have a "start this after that starts"


Xen-users mailing list