From e2d68f265f985e891b85b972ba8015cab9f52fab Mon Sep 17 00:00:00 2001 From: guygma Date: Fri, 9 Jun 2017 11:42:16 -0400 Subject: [PATCH] Create systemd.markdown (#2790) --- source/_docs/autostart/systemd.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index c829df3312d..60ad4084fc6 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -22,7 +22,7 @@ If you want Home Assistant to be launched automatically, an extra step is needed - `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location. - If running Home Assistant in a Python virtual environment or a Docker container, please skip to section below. -- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as - normally `homeassistant`. For Ubuntu 16.04, the file is `/lib/systemd/system/home-assistant.service` and requires running this command `sudo ln -s /lib/systemd/system/home-assistant.service /etc/systemd/system/home-assistant.service` after file is created. +- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as - normally `homeassistant`. In particular, this is the case for Ubuntu 16.04. - If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file. Ex. `sudo nano -w /etc/systemd/system/home-assistant@[your user].service`. After text entered, press CTRL-X then press Y to save and exit. ```