http://bugzilla.suse.com/show_bug.cgi?id=1011053 http://bugzilla.suse.com/show_bug.cgi?id=1011053#c16 --- Comment #16 from zhen ren <zren@suse.com> --- (In reply to Marcus Meissner from comment #15)

meaning what will happen on systems withiout LVM or similar?

Only harmless influence on lvm and device-mapper RPMs.

will there be breakage?

No.

will there be a useless service running?

I enabled 2 systemd units in this MU: 1. dm-event.socket just socket-based activation, 'dmeventd' will be started on demand; 2. lvm2-monitor.service This service will default to running. But, I doesn't see any real load except for a running service. What this service does is just telling 'dmeventd' to start/stop to perform real monitoring work for certain volume group. I also take upstream pkg spec file as a reference: """ %post /sbin/ldconfig %systemd_post blk-availability.service lvm2-monitor.service if [ "$1" = "1" ] ; then # enable and start lvm2-monitor.service on completely new installation only, not on upgrades systemctl enable lvm2-monitor.service systemctl start lvm2-monitor.service fi """ So, I think it's safe and deserved to enable them:) -- You are receiving this mail because: You are on the CC list for the bug.