I'm trying to create a systemd user unit and have it start when the system boots. The service does start manually, however it does not start at boot.From searching the Internet I learned that in order for user units to start at boot, I supposedly need to run loginctl enable-linger <username>, but this seems to have had no effect at all. Indeed, the man page says:       Enable/disable user lingering for one or more users. If enabled for       a specific user, a user manager is spawned for the user at boot and       kept around after logouts. This allows users who are not logged in       to run long-running services.Despite running this command, my service doesn't start at boot.loginctl enable-linger errorThe unit:$ cat ~/.config/systemd/user/thin\@.service[Unit]Description=A fast and very simple Ruby web server[Service]Type=simpleEnvironmentFile=/home/error/.config/thin/%iExecStart=/usr/bin/bash /home/error/.rvm/wrappers/%i/thin start -a $THIN_BIND -p $THIN_PORTWorkingDirectory=/srv/www/%iPrivateTmp=true[Install]WantedBy=multi-user.targetWhen I reboot, it is not running:$ systemctl --user status thin@redmine -l thin@redmine.service - A fast and very simple Ruby web server   Loaded: loaded (/home/error/.config/systemd/user/thin@.service; enabled; vendor preset: enabled)   Active: inactive (dead)# systemctl status user@1000 -l user@1000.service - User Manager for UID 1000   Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled)   Active: active (running) since Wed 2015-12-23 19:43:27 GMT; 13s ago Main PID: 613 (systemd)   Status: Startup finished in 38ms.   CGroup: /user.slice/user-1000.slice/user@1000.service           613 /usr/lib/systemd/systemd --user           615 (sd-pam)                                                          Dec 23 19:43:27 redmine systemd[613]: Reached target Sockets.Dec 23 19:43:27 redmine systemd[613]: Starting Sockets.Dec 23 19:43:27 redmine systemd[613]: Reached target Timers.Dec 23 19:43:27 redmine systemd[613]: Starting Timers.Dec 23 19:43:27 redmine systemd[613]: Reached target Basic System.Dec 23 19:43:27 redmine systemd[613]: Starting Basic System.Dec 23 19:43:27 redmine systemd[613]: Reached target Default.Dec 23 19:43:27 redmine systemd[613]: Startup finished in 38ms.Dec 23 19:43:27 redmine systemd[613]: Starting Default.Dec 23 19:43:27 redmine systemd[1]: Started User Manager for UID 1000.I can start it manually, and it works:$ systemctl --user start thin@redmine$ systemctl --user status thin@redmine -l thin@redmine.service - A fast and very simple Ruby web server   Loaded: loaded (/home/error/.config/systemd/user/thin@.service; enabled; vendor preset: enabled)   Active: active (running) since Wed 2015-12-23 19:43:50 GMT; 5s ago Main PID: 1265 (ruby)   CGroup: /user.slice/user-1000.slice/user@1000.service/thin.slice/thin@redmine.service           1265 ruby /home/error/.rvm/gems/ruby-2.2.1@redmine/bin/thin start -a ::1 -p 8008Dec 23 19:43:50 redmine systemd[613]: Started A fast and very simple Ruby web server.Dec 23 19:43:50 redmine systemd[613]: Starting A fast and very simple Ruby web server...Dec 23 19:43:52 redmine bash[1265]: /home/error/.rvm/gems/ruby-2.2.1@redmine/gems/htmlentities-4.3.1/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: inodot# systemctl status user@1000 -l user@1000.service - User Manager for UID 1000   Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled)   Active: active (running) since Wed 2015-12-23 19:43:27 GMT; 40s ago Main PID: 613 (systemd)   Status: Startup finished in 38ms.   CGroup: /user.slice/user-1000.slice/user@1000.service           613 /usr/lib/systemd/systemd --user           615 (sd-pam)                                                                  thin.slice             thin@redmine.service               1265 ruby /home/error/.rvm/gems/ruby-2.2.1@redmine/bin/thin start -a ::1 -p 8008                                                               Dec 23 19:43:27 redmine systemd[613]: Startup finished in 38ms.Dec 23 19:43:27 redmine systemd[613]: Starting Default.Dec 23 19:43:27 redmine systemd[1]: Started User Manager for UID 1000.Dec 23 19:43:50 redmine systemd[613]: Created slice -.slice.Dec 23 19:43:50 redmine systemd[613]: Starting -.slice.Dec 23 19:43:50 redmine systemd[613]: Created slice thin.slice.Dec 23 19:43:50 redmine systemd[613]: Starting thin.slice.Dec 23 19:43:50 redmine systemd[613]: Started A fast and very simple Ruby web server.Dec 23 19:43:50 redmine systemd[613]: Starting A fast and very simple Ruby web server...Dec 23 19:43:52 redmine bash[1265]: /home/error/.rvm/gems/ruby-2.2.1@redmine/gems/htmlentities-4.3.1/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: inodotHow do I figure out why this service doesn't start at boot, and get it to do so?The operating system is Fedora 23 x86_64, systemd 222-10.
Why doesn't my systemd user unit start at boot?
fedora;systemd;services;not root user
Figures that I'd figure this out on my own.The clue was here, in the user service output:Dec 23 19:43:27 redmine systemd[613]: Reached target Default.My unit was asking to be loaded with multi-user.target, but there is no such target in the user systemd.I changed this to default.target in the unit file, disabled and re-enabled the service, and it now starts at boot time.[Install]WantedBy=default.targetand then$ systemctl --user disable thin@redmineRemoved symlink /home/error/.config/systemd/user/multi-user.target.wants/thin@redmine.service.$ systemctl --user daemon-reload$ systemctl --user enable thin@redmineCreated symlink from /home/error/.config/systemd/user/default.target.wants/thin@redmine.service to /home/error/.config/systemd/user/thin@.service.