aboutsummaryrefslogtreecommitdiffstats
path: root/tools/libxc/xc_linux_save.c
diff options
context:
space:
mode:
authoriap10@tetris.cl.cam.ac.uk <iap10@tetris.cl.cam.ac.uk>2005-06-17 21:44:11 +0000
committeriap10@tetris.cl.cam.ac.uk <iap10@tetris.cl.cam.ac.uk>2005-06-17 21:44:11 +0000
commit227aeb4d79e2f90bae5048a26ebd6dc040a7d9f2 (patch)
tree4c6efc63b5d443a5e6964711cf8cbb18b9960c1b /tools/libxc/xc_linux_save.c
parent86d6165ed3685109216376bb183ff829036d5b40 (diff)
downloadxen-227aeb4d79e2f90bae5048a26ebd6dc040a7d9f2.tar.gz
xen-227aeb4d79e2f90bae5048a26ebd6dc040a7d9f2.tar.bz2
xen-227aeb4d79e2f90bae5048a26ebd6dc040a7d9f2.zip
bitkeeper revision 1.1717 (42b3442b7kXKhXN5lvR9spIGT5LsYQ)
When xend starts, it fires off xcs. If you're running on a slow machine its possible that xcs started but xend didnt wait long enough to notice. The attached patch loops several times while waiting for xcs to come up. It seems to be working here while the original is not (slow machine here). From: Tim Newsham [newsham@lava.net] Signed-off-by: ian@xensource.com
Diffstat (limited to 'tools/libxc/xc_linux_save.c')
0 files changed, 0 insertions, 0 deletions