On 11/10/19 10:25 AM, sixpack13 wrote:
okay, journalctl | grep -i lvm => Nov 08 03:07:27 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 03:07:27 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 08 07:58:17 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 07:58:17 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 04:27:58 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 04:27:58 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 19:57:28 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 19:57:28 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. systemctl | grep -i lvm: => lvm2-lvmpolld.socket loaded active listening LVM2 poll daemon socket any /dev/sdc - /dev/sdf entries here ?
Nope.... But the point is, they can appear and they do appear on multiple systems here which don't have lvm partitions. I'm not going to spend any time to determine when they do and when they don't. They appear here on multiple systems, with no lvm, at shutdown with no problems to poweroff. So, the message are benign, IMO. Most people don't bother to do this. But since you're not using lvm you may want to consider disabling lvm2-lvmpolld.socket and lvm2-monitor.service. As for selinux. Instead of trying to check the logs, it is probably easier to use the GUI sealert to check. So, if there is an selinux issue one can diagnose it. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
