Zdenek Kabelac 194eccf925 dmeventd: lvm2 plugin uses envvar registry ... Thin plugin started to use configuble setting to allow to configure usage of external scripts - however to read this value it needed to execute internal command as dmeventd itself has no access to lvm.conf and the API for dmeventd plugin has been kept stable. The call of command itself was not normally 'a big issue' until users started to use higher number of monitored LVs and execution of command got stuck because other monitored resource already started to execute some other lvm2 command and become blocked waiting on VG lock. This scenario revealed necesity to somehow avoid calling lvm2 command during resource registration - but this requires bigger changes - so meanwhile this patch tries to minimize the possibility to hit this race by obtaining any configurable setting just once - such patch is small and covers majority of problem - yet better solution needs to be introduced likely with bigger rework of dmeventd. TODO: avoid blocking registration of resource with execution of lvm2 commands since those can get stuck waiting on mutexes.		2018-10-10 09:54:07 +02:00
..
plugins	dmeventd: lvm2 plugin uses envvar registry	2018-10-10 09:54:07 +02:00
.exported_symbols	Add rudimentary versioning to the dmevend protocol, allowing us to detect the	2011-04-04 16:11:09 +00:00
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
dmeventd.c	build: include configure.h	2018-06-22 23:11:44 +02:00
dmeventd.h	doc: change fsf address	2016-01-21 12:11:37 +01:00
libdevmapper-event.c	dmeventd: base vdo plugin	2018-07-09 15:28:32 +02:00
libdevmapper-event.h	cleanup: avoid gcc warns	2016-04-08 20:20:16 +02:00
libdevmapper-event.pc.in	device-mapper: Fork libdm internally.	2018-05-16 13:00:50 +01:00
Makefile.in	build: libbase.a	2018-06-04 13:53:07 +01:00