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:
stat64("/usr/research/proj/xen/i386/xen-3.2.0/dist/install/usr/lib/python/xen/xend/XendLogging.py")
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
/usr/research/proj/xen/i386/xen-3.2.0/dist/install/usr/lib/python/xen/xend/XendLogging.py
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
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
