summaryrefslogtreecommitdiff
path: root/meta-phosphor/common/recipes-phosphor/state/files
diff options
context:
space:
mode:
authorAndrew Geissler <andrewg@us.ibm.com>2017-07-27 01:53:04 +0300
committerPatrick Williams <patrick@stwcx.xyz>2017-08-03 04:54:52 +0300
commit4ec27746b6bcfa342a7f1e9e465524333d57b9c2 (patch)
tree16f4c95a3ef797b74e4aabd01073c4da8f75ea8e /meta-phosphor/common/recipes-phosphor/state/files
parent8861a87675343dae4f03eb3708cf8dbbeea3a506 (diff)
downloadopenbmc-4ec27746b6bcfa342a7f1e9e465524333d57b9c2.tar.xz
Add in new host reboot target
The state management code on the BMC is designed to utilize systemd targets as much as possible. The host reboot was always the odd duck that had some special code written to support it. This special code would basically issue a power off, look for it to complete and then issue a power on. This is very error prone code and has resulted in a few issues. Moving to a single systemd target (the new reboot target) defined here will allow the host reboots to occur solely through a single systemd target now. openbmc/openbmc#2032 is one of those bugs being addressed with this change. Change-Id: If33454aa4f15580e45f888a9b1602dec24a46fca Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
Diffstat (limited to 'meta-phosphor/common/recipes-phosphor/state/files')
-rw-r--r--meta-phosphor/common/recipes-phosphor/state/files/phosphor-reboot-host@.service11
1 files changed, 11 insertions, 0 deletions
diff --git a/meta-phosphor/common/recipes-phosphor/state/files/phosphor-reboot-host@.service b/meta-phosphor/common/recipes-phosphor/state/files/phosphor-reboot-host@.service
new file mode 100644
index 0000000000..fdf84c1f33
--- /dev/null
+++ b/meta-phosphor/common/recipes-phosphor/state/files/phosphor-reboot-host@.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=Reboot host%i
+Wants=obmc-host-stop@%i.target
+After=obmc-host-stop@%i.target
+
+[Service]
+ExecStart={base_bindir}/systemctl start obmc-host-start@%i.target
+
+
+[Install]
+WantedBy=obmc-host-reboot@%i.target