Daniel P. Berrange 32d6c7386d Print hex values with '0x' prefix and octal with '0' in debug messages ... Seeing a log message saying 'flags=93' is ambiguous & confusing unless you happen to know that libvirt always prints flags as hex. Change our debug messages so that they always add a '0x' prefix when printing flags, and '0' prefix when printing mode. A few other misc places gain a '0x' prefix in error messages too. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>		2017-09-25 13:34:53 +01:00
..
domain_lock.c
domain_lock.h
libvirt_lockd.aug
libvirt_sanlock.aug
lock_daemon_config.c
lock_daemon_config.h
lock_daemon_dispatch.c
lock_daemon_dispatch.h
lock_daemon.c	maint: Fix incorrect parenthesis placement causing true/false assignment	2017-09-05 11:27:12 +02:00
lock_daemon.h
lock_driver_lockd.c	Print hex values with '0x' prefix and octal with '0' in debug messages	2017-09-25 13:34:53 +01:00
lock_driver_lockd.h
lock_driver_nop.c	Print hex values with '0x' prefix and octal with '0' in debug messages	2017-09-25 13:34:53 +01:00
lock_driver_nop.h
lock_driver_sanlock.c	Print hex values with '0x' prefix and octal with '0' in debug messages	2017-09-25 13:34:53 +01:00
lock_driver.h
lock_manager.c	Print hex values with '0x' prefix and octal with '0' in debug messages	2017-09-25 13:34:53 +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	man: Fix documentation errors about the paths of the config files	2017-06-28 11:07:08 +02:00
virtlockd.service.in
virtlockd.socket.in
virtlockd.sysconf