lvm2/scripts/lvm2_lvmetad_systemd_red_hat.socket.in

[Unit]
Description=LVM2 metadata daemon socket
Documentation=man:lvmetad(8)
DefaultDependencies=no

[Socket]
ListenStream=@DEFAULT_RUN_DIR@/lvmetad.socket
SocketMode=0600
RemoveOnStop=true

[Install]
WantedBy=sysinit.target
Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad systemd units and add ExecStartPost=vgscan to actually run the first scan that will fill the metadata daemon with metadata information. 2012-02-23 17:31:49 +04:00			`[Unit]`
			`Description=LVM2 metadata daemon socket`
systemd: Add Documentation references These documentation references show up in "systemctl status" output. 2012-06-20 16:23:50 +04:00			`Documentation=man:lvmetad(8)`
Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad systemd units and add ExecStartPost=vgscan to actually run the first scan that will fill the metadata daemon with metadata information. 2012-02-23 17:31:49 +04:00			`DefaultDependencies=no`

			`[Socket]`
lvmetad.socket 2012-02-27 19:45:49 +04:00			`ListenStream=@DEFAULT_RUN_DIR@/lvmetad.socket`
Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad systemd units and add ExecStartPost=vgscan to actually run the first scan that will fill the metadata daemon with metadata information. 2012-02-23 17:31:49 +04:00			`SocketMode=0600`
systemd: use RemoveOnStop for dm-event.socket and lvm2-lvmetad.socket Systemd version 214 introduced new "RemoveOnStop" option for socket units to remove the socket/FIFO when the particular unit is stopped. Also https://bugzilla.redhat.com/show_bug.cgi?id=802748. 2014-06-13 17:45:25 +04:00			`RemoveOnStop=true`
Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad systemd units and add ExecStartPost=vgscan to actually run the first scan that will fill the metadata daemon with metadata information. 2012-02-23 17:31:49 +04:00
			`[Install]`
systemd: make sysinit.target to pull in lvm2-lvmetad.socket, not sockets.target The sysinit.target is ordered even before sockets.target and there may be situations in which the lvmetad is needed early, for example in rescue.target to activate some LVs on which mountpoints reside. Also, like in the case of rescue.target, the sockets.target is not pulled in (unless some other service pulls it in explicitly). See also: https://bugzilla.redhat.com/show_bug.cgi?id=1087586#c26 for the summary of the problem. 2014-04-30 16:52:10 +04:00			`WantedBy=sysinit.target`