diff --git a/docs/FAQ.html b/docs/FAQ.html
index 5819afc98a..57723fbae1 100644
--- a/docs/FAQ.html
+++ b/docs/FAQ.html
@@ -40,6 +40,13 @@ A:link, A:visited, A:active { text-decoration: underline }
Or from a configured tree with:
make rpm
+ Failure to use the API for non-root users
+ Large parts of the API are only accessible as root, however the read
+ only access to the xenstore data doesnot have to be forbidden to user, at
+ least for monitoring purposes. If "virsh info" fails to run as an user,
+ change the mode of the xenstore read-only socket with:
+ chmod 666 /var/run/xenstored/socket_ro
+
- What is the process to compile libvir ?
As most UNIX libraries libvir follows the "standard":
gunzip -c libvir-xxx.tar.gz | tar xvf -
diff --git a/docs/bugs.html b/docs/bugs.html
index e8e6b69f7a..e4d4275fe9 100644
--- a/docs/bugs.html
+++ b/docs/bugs.html
@@ -11,8 +11,7 @@ A:link, A:visited, A:active { text-decoration: underline }
with an on-line
archive. Please subscribe to this list before posting by visiting the associated Web
page and follow the instructions. Patches with explanations and provided as
-attachments are really appreciated and will be discussed on the mailing
-list. If possible generate the patches by using cvs diff -u in a CVS
-checkout.We expect to use Red Hat
+attachments are really appreciated and will be discussed on the mailing list.
+If possible generate the patches by using cvs diff -u in a CVS checkout.
We expect to use Red Hat
Bugzilla to track bugs for libvir, though there isn't yet a libvir
software module.
Daniel Veillard