lvm2/scripts/lvm2_lvmetad_systemd_red_hat.service.in

[Unit]
Description=LVM2 metadata daemon
Documentation=man:lvmetad(8)
Requires=lvm2-lvmetad.socket
After=lvm2-lvmetad.socket
DefaultDependencies=no
Conflicts=shutdown.target

[Service]
Type=forking
NonBlocking=true
ExecStart=@sbindir@/lvmetad
ExecReload=@sbindir@/lvmetad -R
Environment=SD_ACTIVATION=1
Restart=on-abort
PIDFile=@LVMETAD_PIDFILE@

[Install]
WantedBy=sysinit.target
Add LVMetaD systemd units. 2012-02-23 11:24:07 +00:00			`[Unit]`
			`Description=LVM2 metadata daemon`
systemd: Add Documentation references These documentation references show up in "systemctl status" output. 2012-06-20 14:23:50 +02:00			`Documentation=man:lvmetad(8)`
Add LVMetaD systemd units. 2012-02-23 11:24:07 +00:00			`Requires=lvm2-lvmetad.socket`
			`After=lvm2-lvmetad.socket`
			`DefaultDependencies=no`
			`Conflicts=shutdown.target`

			`[Service]`
			`Type=forking`
LVMetaD socket operates in non-blocking mode. 2012-02-28 13:07:03 +00:00			`NonBlocking=true`
Add LVMetaD systemd units. 2012-02-23 11:24:07 +00:00			`ExecStart=@sbindir@/lvmetad`
			`ExecReload=@sbindir@/lvmetad -R`
Use SD_ACTIVATION env. var. in systemd units to better detect systemd in use. LISTEN_PID and LISTEN_FDS environment variables are defined only during systemd "start" action. But we still need to know whether we're activated during "reload" action as well - we use the reload action to call "dmeventd -R"/"lvmetad -R" for statefull daemon restart. We can't use normal "restart" as that is simply composed of "stop" and "start" and we would lose any state the daemon has. 2012-03-14 15:51:51 +00:00			`Environment=SD_ACTIVATION=1`
Add 'Restart: on-abort' for lvmetad systemd service. Restart lvmetad automatically if it exits due to reception of uncaught signal, leaving a track in systemd log/syslog. 2012-03-08 09:49:09 +00:00			`Restart=on-abort`
configure: run directory configuration cleanup There were several hard-coded values for run directory around the code. Also, some tools are DM specific only, others are LVM specific and there was no distinction made here before. With this patch applied, we have this cleaned up a bit (subsystem in brackets, defaults in parentheses): [common] configurable PID_DIR (/var/run) lvm [lvm] configurable RUN_DIR (/var/run/lvm) configurable locking dir (/var/lock/lvm) clvmd [lvm] configurable pid file (PID_DIR/clvmd.pid) socket (RUN_DIR/clvmd.sock) lvmetad [lvm] configurable pid file (PID_DIR/lvmetad.pid) socket (RUN_DIR/lvmetad.socket) dm [dm] configurable DM_RUN_DIR (/var/run) cmirrord [dm] configurable pid file (PID_DIR/cmirrord.pid) dmeventd [dm] configurable pid file (PID_DIR/dmeventd.pid) server fifo (DM_RUN_DIR/dmeventd-server) client fifo (DM_RUN_DIR/dmeventd-client) The changes briefly: - added configure --with-default-pid-dir - added configure --with-default-dm-run-dir - added configure --with-lvmetad-pidfile - by default, using one common pid directory for everything (only lvmetad was not following this before) 2012-06-21 08:41:52 -04:00			`PIDFile=@LVMETAD_PIDFILE@`
Add LVMetaD systemd units. 2012-02-23 11:24:07 +00:00
			`[Install]`
			`WantedBy=sysinit.target`