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

[Xen-devel] Re: [Xen-users] Problem running xenmon

To: Anand <xen.mails@xxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-users] Problem running xenmon
From: Diwaker Gupta <diwaker.lists@xxxxxxxxx>
Date: Fri, 13 Jan 2006 15:03:46 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Jan 2006 23:10:36 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MHUyrNyJzPr9N8iEsLO+oAwg6UUZgvT8Mv5OGq6Khmx1gBYZCH8BpusWk4hbQZGyBVPDNw2PL6WYh4MT8Xx/f9zGfMLgYjlI2hE/1iICODdB80VVbxwd+8LUAtlGE0fFXp7HPEOgOMo4RTdryqJ9zxd8H6s4WlOr/o4q5GKEmII=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <acb757c00601131316j4bebb104x16ed2f9d761b6611@xxxxxxxxxxxxxx>
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: <5f74ce410601111415u49451f9ax8cb44df17f1e3b3f@xxxxxxxxxxxxxx> <acb757c00601131316j4bebb104x16ed2f9d761b6611@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 1/13/06, Anand <xen.mails@xxxxxxxxx> wrote:
> Once you have run those, go to the xenmon directory. Make sure xenbaked is
> copied to a directory which is in your path (xenmon.py needs that). I copied
> xenbaked to /usr/sbin/

If you are installing from source, then doing the regular make install
should copy all the binaries at appropriate locations. You should NOT
have to copy them yourself manually. On my machine, Xen puts its
binaries in /usr/local/sbin

> python xenmon.py

You should not have to do this either. If doing a 'make install', Xen
will make xenmon.py executable and the shell should automatically
invoke the python interpreter for you.

Can you please try running just 'xenmon.py' and see if that works for you?

Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>