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


[Xen-users] xend embedded pyc path

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xend embedded pyc path
From: David Becker <becker@xxxxxxxxxxx>
Date: Fri, 23 May 2008 16:48:49 -0400
Delivery-date: Fri, 23 May 2008 13:49:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
After a recent power cycle of our building, I discovered that the xend pyc
files have full paths to the install directory where I built the xen tools.
Turns out the xend python process calls stat() on these pyc filenames.
In this case, the automounter was broken so the stat() hung and xend failed
to start.

I was very suprised to see the full path to the dist/install *.py files
in the strace output.

For example, strace showed xend python making this call:

The file is on that host at  /usr/lib/python/xen/xend/XendLogging.py

The pyc file does contain the path:
# strings /usr/lib/python/xen/xend/XendLogging.pyc | grep dist

Why is pyton stat'ing files back in the dist/install area?
How do I build xen tools so these stat calls only go to /usr/lib?

- David

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] xend embedded pyc path, David Becker <=