On Wed, Oct 24, 2012 at 19:05:01 +0200, Michal Privoznik wrote:
through which user set under what permissions does sanlock
daemon run so libvirt will set the same permissions for
files exposed to it.
---
docs/locking.html.in | 22 +++++++++
src/locking/libvirt_sanlock.aug | 2 +
src/locking/lock_driver_sanlock.c | 76 ++++++++++++++++++++++++++++++-
src/locking/sanlock.conf | 11 ++++-
src/locking/test_libvirt_sanlock.aug.in | 2 +
5 files changed, 111 insertions(+), 2 deletions(-)
...
diff --git a/src/locking/sanlock.conf b/src/locking/sanlock.conf
index efc35ee..40ece65 100644
--- a/src/locking/sanlock.conf
+++ b/src/locking/sanlock.conf
@@ -29,7 +29,8 @@
#
# Recommendation is to just mount this default location as
# an NFS volume. Uncomment this, if you would prefer the mount
-# point to be somewhere else.
+# point to be somewhere else. Moreover, please make sure
+# sanlock daemon can access the specified path.
#
#disk_lease_dir = "/var/lib/libvirt/sanlock"
Since this directory is created by libvirt.spec in lock-sanlock subpackage, I
think the specfile should make sure the directory is created in a way that
default installation of sanlock is able to access it, i.e., it should be
accessible for group sanlock.
Jirka