summaryrefslogtreecommitdiff
path: root/tools/lvmcmdlib.c
diff options
context:
space:
mode:
authorPetr Rockai <prockai@redhat.com>2011-10-19 08:46:26 +0000
committerPetr Rockai <prockai@redhat.com>2011-10-19 08:46:26 +0000
commit61cf772e70b99ef000a55194d71ddebcfeb9d8d7 (patch)
tree36b2940dc38c5ac08936c947d4bef09546b2d65d /tools/lvmcmdlib.c
parentdc0582ce0aeeeac85831465ca1efa15c7bba78ec (diff)
downloadlvm2-61cf772e70b99ef000a55194d71ddebcfeb9d8d7.tar.gz
Keep the LVM-based dmeventd plugins from trying to manipulate the dmeventd
monitoring state of the logical volumes they are currently acting on. Until now, every time a logical volume has been changed by a dmeventd plugin, this plugin would have called back to dmeventd through the external FIFO mechanism. I am fairly sure this was superfluous, inefficient and possibly even dangerous.
Diffstat (limited to 'tools/lvmcmdlib.c')
-rw-r--r--tools/lvmcmdlib.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/tools/lvmcmdlib.c b/tools/lvmcmdlib.c
index 6b2bc9d10..47bf1c888 100644
--- a/tools/lvmcmdlib.c
+++ b/tools/lvmcmdlib.c
@@ -97,6 +97,10 @@ int lvm2_run(void *handle, const char *cmdline)
return ret;
}
+void lvm2_disable_dmeventd_monitoring(void *handle) {
+ init_dmeventd_monitor(DMEVENTD_MONITOR_IGNORE);
+}
+
void lvm2_log_level(void *handle, int level)
{
struct cmd_context *cmd = (struct cmd_context *) handle;