From 83a743f8b5ac7dd43d3ca3ac1a7a81e882ef9dc0 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 9 Apr 2016 10:33:34 +0200 Subject: [PATCH] Add more details (fix for #368) --- source/getting-started/autostart.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/autostart.markdown b/source/getting-started/autostart.markdown index 77b9cdc1e6e..72e76957e59 100644 --- a/source/getting-started/autostart.markdown +++ b/source/getting-started/autostart.markdown @@ -51,7 +51,7 @@ $ ps -p 1 -o comm= If the preceding command returns the string `systemd`, you are likely using `systemd`. -If you want Home Assistant to be launched automatically, an extra step is needed to setup `systemd`. You need a service file to control Home Assistant with `systemd`. If you are using a Raspberry Pi then replace the `[your user]` with `pi` otherwise use your user you want to run Home Assistant. +If you want Home Assistant to be launched automatically, an extra step is needed to setup `systemd`. You need a service file to control Home Assistant with `systemd`. If you are using a Raspberry Pi with Raspbian then replace the `[your user]` with `pi` otherwise use your user you want to run Home Assistant. `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location. ```bash $ su -c 'cat <> /lib/systemd/system/home-assistant@[your user].service