Peter Rajnoha cf9927697b Suppress low-level locking errors and warnings while using --sysinit. ... Today, we use "suppress_messages" flag (set internally in init_locking fn based on 'ignorelockingfailure() && getenv("LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES")'. This way, we can suppress high level messages like "File-based locking initialisation failed" or "Internal cluster locking initialisation failed". However, each locking has its own sequence of initialization steps and these could log some errors as well. It's quite misleading for the user to see such errors and warnings if the "--sysinit" is used (and so the ignorelockingfailure && LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES environment variable). Errors and warnings from these intermediary steps should be suppressed as well if requested. This patch propagates the "suppress_messages" flag deeper into locking init functions. I've also added these flags for other locking types for consistency, though it's not actually used for no_locking and readonly_locking.		2011-08-09 11:44:57 +00:00
..
log.c	pre-release clean-ups	2011-04-29 00:21:13 +00:00
log.h	Suppress low-level locking errors and warnings while using --sysinit.	2011-08-09 11:44:57 +00:00
lvm-logging.h	Suppress duplicate error messages about read failures and missing devices.	2010-05-05 22:37:52 +00:00