# HG changeset patch
# User kaf24@scramble.cl.cam.ac.uk
# Date 1074906835 0
# Node ID cc2a9e8d15689be641e9dba52156f4cb2df43a31
# Parent  85909caca7ed513d9f3ecf96c1cf544883d85089
bitkeeper revision 1.691 (4011c6d3g_Q_DeG3-esCCO1ROch6Rw)

XenoUtil.py, VBD-HOWTO.txt:
  Fix location of xen vbd dataase file.


diff -r 85909caca7ed -r cc2a9e8d1568 docs/VBD-HOWTO.txt
--- a/docs/VBD-HOWTO.txt	Fri Jan 23 20:32:19 2004 +0000
+++ b/docs/VBD-HOWTO.txt	Sat Jan 24 01:13:55 2004 +0000
@@ -86,7 +86,7 @@ Virtual Disk Management
 The VD management code runs entirely in userspace.  The code is written in
 Python and can therefore be accessed from custom scripts, as well as from the
 convenience scripts provided.  The underlying VD database is a SQLite database
-in /var/spool/xen_vdisks.sqlite.
+in /var/lib/xen_vdisks.sqlite.
 
 The scripts provided are as follows:
 
@@ -131,7 +131,7 @@ More detail:
 
 When you use vd_format.py to add a device to the free space pool, the device is
 logically split up into extents.  These extents are recorded in the Virtual
-Disk Management database in /var/spool/xen_vdisks.sqlite.
+Disk Management database in /var/lib/xen_vdisks.sqlite.
 
 When you use vd_create.py to add create a virtual disk, some of the extents in
 the free space pool are reallocated for that virtual disk and a record for that
diff -r 85909caca7ed -r cc2a9e8d1568 tools/xc/py/XenoUtil.py
--- a/tools/xc/py/XenoUtil.py	Fri Jan 23 20:32:19 2004 +0000
+++ b/tools/xc/py/XenoUtil.py	Sat Jan 24 01:13:55 2004 +0000
@@ -3,9 +3,9 @@ import string, re, os, sys
 ##### Module variables
 
 """Location of the Virtual Disk management database.
-   defaults to /var/spool/xen_vdisks.sqlite
+   defaults to /var/lib/xen_vdisks.sqlite
 """
-VD_DB_FILE = "/var/spool/xen_vdisks.sqlite"
+VD_DB_FILE = "/var/lib/xen_vdisks.sqlite"
 
 """VBD expertise level - determines the strictness of the sanity checking.
   This mode determines the level of complaints when disk sharing occurs