summaryrefslogtreecommitdiffstats
path: root/scripts/lvm2_activation_generator_systemd_red_hat.c
Commit message (Collapse)AuthorAgeFilesLines
* systemd: O_CLOEXEC not needed in activation generatorPeter Rajnoha2012-08-011-1/+1
| | | | | O_CLOEXEC not actually needed, this is just a simple program, it is not supposed to fork/exec anywhere and anytime in the future.
* systemd: add lvm2 activation generatorPeter Rajnoha2012-07-311-0/+169
The lvm2 activation generator generates systemd units conditionally based on the global/use_lvmetad lvm.conf setting. If use_lvmetad=0, the lvm2-activation-early.service and lvm2-activation.service units will be generated. These units are responsible for direct volume activation by calling "vgchange -aay --sysinit" (this is actually the original on-boot activation as it was used before). If use_lvmetad=1, no units will be generated as we're relying on autoactivation. Important thing to note is that the lvm2-activation units normally bring in the udev-settle ("storage-wait") service that waits for udev to settle (with block devices). We don't need this if lvmetad is used in conjunction with autoactivation feature... but systemd units can't be enabled or disabled (or dependencies added/removed) dynamically based on external configuration. Therefore, we need the unit generator which adds support for such situations: the units as a whole either exist or not based on the external configuration.