lvm2/scripts/lvm2_monitoring_systemd_red_hat.service.in

[Unit]
Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8)
Requires=dm-event.socket lvm2-lvmetad.socket
After=dm-event.socket dm-event.service lvm2-lvmetad.socket lvm2-activation.service lvm2-lvmetad.service
Before=local-fs-pre.target
DefaultDependencies=no
Conflicts=shutdown.target

[Service]
Type=oneshot
Environment=LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES=1
ExecStart=@sbindir@/lvm vgchange --monitor y --ignoreskippedcluster
ExecStop=@sbindir@/lvm vgchange --monitor n --ignoreskippedcluster
RemainAfterExit=yes

[Install]
WantedBy=sysinit.target
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`[Unit]`
			`Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling`
systemd: Add Documentation references These documentation references show up in "systemctl status" output. 2012-06-20 14:23:50 +02:00			`Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8)`
systemd: various updates and fixes Don't use lvmetad in lvm2-monitor.service ExecStop to avoid a systemd issue. - a systemd design issue while processing dependencies with socket-based activation that ends up with a hang - https://bugzilla.redhat.com/show_bug.cgi?id=843587 (also tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=871527) - not using lvmetad in this case is just a workaround, once the bug above is resolved, we should enable the lvmetad in that specific case Remove dependency on fedora-storage-init.service in lvm2 systemd units. - fedora-storage-init.service and fedora-storage-init-late.service is going to be separated into respective units that belong to each block device subsystem: - mpath + mdraid activated via udev solely - dmraid with its own dmraid-activation.service unit - lvm2 with the lvm2-activation-generator to generate the activation units runtime if lvmetad disabled (global/use_lvmetad=0 set in lvm.conf) and activation done via udev+lvmetad if lvmetad enabled (global/use_lvmetad=1 set in lvm.conf) Depend on lvm2-lvmetad.socket in lvm2-monitor.service systemd unit. - as lvm2-monitor uses lvmetad if lvmetad is enabled 2012-10-30 20:36:49 +01:00			`Requires=dm-event.socket lvm2-lvmetad.socket`
systemd: stop lvm2-monitor.service before dm-event.service 2015-03-31 15:50:16 +02:00			`After=dm-event.socket dm-event.service lvm2-lvmetad.socket lvm2-activation.service lvm2-lvmetad.service`
systemd: use {local,remote}-fs-pre.target instead of {local,remote}-fs.target We want most of our units to be started before any local/remote mount points are mounted - we used {local,remote}-fs.target for this purpose before, but it was not 100% correct as there's even {local,remote}-fs-pre.target special systemd unit reserved for this exact purpose. See also man 7 systemd.special and "local-fs-pre.target"/"remote-fs-pre.target" description. 2015-09-23 13:17:12 +02:00			`Before=local-fs-pre.target`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`DefaultDependencies=no`
			`Conflicts=shutdown.target`

			`[Service]`
			`Type=oneshot`
Suppress locking error messages in monitoring init scripts. 2011-08-11 15:27:46 +00:00			`Environment=LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES=1`
scripts: use --ignoreskippedcluster in lvm2-monitor initscript/systemd unit When clustered VG is available in the system but we don't have clustering set up for whatever reason, the lvm2-monitor scripts should not fail completely just because these clustered VGs are skipped during vgs/vgchange calls in lvm2-monitor initscript/systemd unit. 2014-02-17 16:25:32 +01:00			`ExecStart=@sbindir@/lvm vgchange --monitor y --ignoreskippedcluster`
systemd: remove workaround for lvm2-monitor.service's ExecStop line Bug https://bugzilla.redhat.com/show_bug.cgi?id=843587 is handled better now - the hang does not occur anymore. There are still error messages issued though during shutdown if someone stops lvm2-lvmetad.service manually that lvm2-monitor.service depends on (even during shutdown). These errors are correct though and will point to incorrect configuration (still having use_lvmetad=1 in lvm.conf and stopping lvm2-lvmetad.service manually). The workaround to prevent the hang is not needed now. So the '--config "global{use_lvmetad=0}"' is now removed from the lvm2-monitor.service's ExecStop line. 2014-10-14 09:56:58 +02:00			`ExecStop=@sbindir@/lvm vgchange --monitor n --ignoreskippedcluster`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`RemainAfterExit=yes`

			`[Install]`
			`WantedBy=sysinit.target`