mirror of
git://sourceware.org/git/lvm2.git
synced 2024-10-26 17:25:10 +03:00
36cac41115
Commitsa29bb6a14b...5c199d99f4narrowed down on addressing the escaping of hyphens in the dynamic creation of manuals whilst avoiding them in creating help texts. This lead to a sequence of slipping through hyphens adrressed by additional patches in aforementioned commit series. On the other hand, postprocessing dynamically man-generator created and statically provided manuals catches all hyphens in need of escaping. Changes: - revert the above commits whilst keeping man-generator streamlining and the detection of any '\' when generating help texts in order to avoid escapes to slip in - Dynamically escape hyphens in manaual pages using sed(1) in the respective Makefile targets - remove any manually added escaping on hyphens from any static manual sources or headers
56 lines
2.3 KiB
Plaintext
56 lines
2.3 KiB
Plaintext
.TH "LVM2-ACTIVATION-GENERATOR" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
|
|
.SH "NAME"
|
|
lvm2-activation-generator - generator for systemd units to activate LVM2 volumes on boot
|
|
.SH SYNOPSIS
|
|
.B #SYSTEMD_GENERATOR_DIR#/lvm2-activation-generator
|
|
.sp
|
|
.SH DESCRIPTION
|
|
The lvm2-activation-generator is called by \fBsystemd\fP(1) on boot
|
|
to generate systemd units at runtime to activate LVM2 volumes if
|
|
\fBlvmetad\fP(8) is disabled (global/use_lvmetad=0 \fBlvm.conf\fP(5)
|
|
option is used). Otherwise, if \fBlvmetad\fP(8) is enabled,
|
|
the lvm2-activation-generator exits immediately without generating
|
|
any systemd units and LVM2 fully relies on event-based activation
|
|
to activate the LVM2 volumes instead using the \fBpvscan\fP(8)
|
|
(pvscan --cache -aay) call that is a part of \fBudev\fP(8) rules.
|
|
|
|
These systemd units are generated by lvm2-activation-generator:
|
|
.sp
|
|
\fIlvm2-activation-early.service\fP
|
|
used for activation of LVM2 volumes that is ordered before systemd's
|
|
special \fBcryptsetup.target\fP to support LVM2 volumes which are not
|
|
layered on top of encrypted devices.
|
|
|
|
\fIlvm2-activation.service\fP
|
|
used for activation of LVM2 volumes that is ordered after systemd's
|
|
special \fBcryptsetup.target\fP to support LVM2 volumes which are
|
|
layered on top of encrypted devices.
|
|
|
|
\fIlvm2-activation-net.service\fP
|
|
used for activation of LVM2 volumes that is ordered after systemd's
|
|
special \fBremote-fs-pre.target\fP to support LVM2 volumes which are
|
|
layered on attached remote devices.
|
|
|
|
Note that all the underlying devices (Physical Volumes) need to be present
|
|
when the service is run. If the there are any devices presented in the system
|
|
anytime later, any LVM2 volumes on top of such devices need to be activated
|
|
directly by \fBlvchange\fP(8) or \fBvgchange\fP(8). This limitation does
|
|
not exist when using \fBlvmetad\fP(8) and accompanying event-based activation
|
|
since such LVM volumes are activated automatically as soon as the Volume Group
|
|
is ready (all the Physical Volumes making up the Volume Group are present
|
|
in the system).
|
|
|
|
The lvm2-activation-generator implements the \fBGenerators Specification\fP
|
|
as referenced in \fBsystemd\fP(1).
|
|
.sp
|
|
.SH SEE ALSO
|
|
.BR lvm.conf (5)
|
|
.BR vgchange (8)
|
|
.BR lvchange (8)
|
|
.BR lvmetad (8)
|
|
.BR pvscan (8)
|
|
.BR udev (7)
|
|
.BR systemd (1)
|
|
.BR systemd.target (5)
|
|
.BR systemd.special (7)
|