On Thu, Mar 15, 2012 at 10:55:20AM -0600, Eric Blake wrote:
> On 03/15/2012 10:35 AM, Daniel P. Berrange wrote:
> > On Thu, Mar 15, 2012 at 05:23:09PM +0100, Peter Krempa wrote:
> >> If the connection to the sanlock daemon is forbidden by selinux the
> >> error message was not clear enough. This pa
On 03/15/2012 10:35 AM, Daniel P. Berrange wrote:
> On Thu, Mar 15, 2012 at 05:23:09PM +0100, Peter Krempa wrote:
>> If the connection to the sanlock daemon is forbidden by selinux the
>> error message was not clear enough. This patch adds a check if proper
>> configuration for selinux is used whil
On Thu, Mar 15, 2012 at 05:23:09PM +0100, Peter Krempa wrote:
> If the connection to the sanlock daemon is forbidden by selinux the
> error message was not clear enough. This patch adds a check if proper
> configuration for selinux is used while trying to connect to sanlock.
>
> *src/locking/lock_
If the connection to the sanlock daemon is forbidden by selinux the
error message was not clear enough. This patch adds a check if proper
configuration for selinux is used while trying to connect to sanlock.
*src/locking/lock_driver_sanlock.c:
- add macro virLockSystemError that checks for
