Bug 1222495 - Enable lvm2-lvmpolld.* units by default
Summary: Enable lvm2-lvmpolld.* units by default
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: rawhide
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 742564 814857
TreeView+ depends on / blocked
 
Reported: 2015-05-18 11:11 UTC by Peter Rajnoha
Modified: 2015-05-20 16:35 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-20 16:35:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Add lvm2-lvmpolld.* to 90-default.preset to enable new lvm2-lvmpolld.* units by default (387 bytes, patch)
2015-05-18 11:11 UTC, Peter Rajnoha
no flags Details | Diff

Description Peter Rajnoha 2015-05-18 11:11:20 UTC
Created attachment 1026662 [details]
Add lvm2-lvmpolld.* to 90-default.preset to enable new lvm2-lvmpolld.* units by default

LVM2 provides a new lvmpolld daemon in recent upstream LVM2 version v2.02.120:

  https://git.fedorahosted.org/cgit/lvm2.git/tree/man/lvmpolld.8.in

We're going to do a new LVM2 build for rawhide to include this daemon and functionality.

We also need to enable lvm2-lvmpolld.* units by default in rawhide because the lvmpolld daemon is replacing the old way which spawned processes directly from  lvm commands which was also not correct way to any background processing in systemd environment. That's (also) why we moved to a separate daemon to do this correctly.

See related bug #742564 and bug #814857.

Patch is attached, it's applicable for current rawhide's systemd git tree.

Comment 1 Zbigniew Jędrzejewski-Szmek 2015-05-19 13:08:31 UTC
f-r is now handling this.

Comment 2 Peter Rajnoha 2015-05-19 13:31:28 UTC
This should be fixed too:

[0] rawhide/~ # rpm -qf /usr/lib/systemd/system-preset/90-default.preset 
systemd-219-13.fc23.x86_64
fedora-release-23-0.12.noarch

Comment 3 Dennis Gilmore 2015-05-20 16:35:55 UTC
fixed in fedora-release-23-0.13


Note You need to log in before you can comment on or make changes to this bug.