Jim Fehlig ee3eddb332 locking: relax PID requirement ...

Some hypervisors like Xen do not have PIDs associated with domains.
Relax the requirement for PID != 0 in the locking code so it can
be used by hypervisors that do not represent domains as a process
running on the host.

Signed-off-by: Jim Fehlig <jfehlig@suse.com>

2015-04-22 14:16:44 -06:00

..

domain_lock.c

sanlock: Don't spam logs with "target pid not found"

2015-03-09 13:36:40 +01:00

domain_lock.h

…

libvirt_lockd.aug

…

libvirt_sanlock.aug

…

lock_daemon_config.c

virconf: Introduce VIR_CONF_ULONG

2014-12-15 10:34:18 +01:00

lock_daemon_config.h

…

lock_daemon_dispatch.c

locking: relax PID requirement

2015-04-22 14:16:44 -06:00

lock_daemon_dispatch.h

…

lock_daemon.c

locking: relax PID requirement

2015-04-22 14:16:44 -06:00

lock_daemon.h

…

lock_driver_lockd.c

locking: relax PID requirement

2015-04-22 14:16:44 -06:00

lock_driver_nop.c

…

lock_driver_nop.h

…

lock_driver_sanlock.c

sanlock: Use VIR_ERR_RESOURCE_BUSY if sanlock_acquire fails

2015-04-15 09:40:42 +02:00

lock_driver.h

sanlock: Don't spam logs with "target pid not found"

2015-03-09 13:36:40 +01:00

lock_manager.c

sanlock: Don't spam logs with "target pid not found"

2015-03-09 13:36:40 +01:00

lock_manager.h

…

lock_protocol.x

…

lockd.conf

…

sanlock_helper.c

…

sanlock.conf

…

test_libvirt_lockd.aug.in

…

test_libvirt_sanlock.aug.in

…

test_virtlockd.aug.in

…

virtlockd.aug

…

virtlockd.conf

…

virtlockd.init.in

…

virtlockd.pod.in

…

virtlockd.service.in

…

virtlockd.socket.in

…

virtlockd.sysconf

…