View difference between Paste ID: uqY2DcGs and KXVdTNrL

-;;; systemd system service example
+;;; systemd user service example
-; See also https://pastebin.com/uqY2DcGs for a user service example.
+; See also https://pastebin.com/KXVdTNrL for a system service example.
 ;
-; Save as this file:  /etc/systemd/system/my-service.service
+; Make sure the directory exists (you only need to do this once):
 ;	mkdir -p ~/.config/systemd/user
 ;
-; in the commands below), as long as it doesn't conflict with any existing system
+; Save this file as:  ~/.config/systemd/user/my-service.service
-; services (see: systemctl list-unit-files '*.service').
+
 ; You can use any name instead of "my-service" of course (but then also adjust that
 ; in the commands below), as long as it doesn't conflict with any existing user
 ; services (see: systemctl --user list-unit-files '*.service').
 ;
 ; The file must have a ".service" suffix but you may omit that suffix in the various
 ; commands below, i.e. you can write "my-service" instead of "my-service.service".
-;	sudo systemctl daemon-reload
+
 ;
 ; Then, tell systemd to reload its configuration:
-;	sudo systemctl start my-service.service
+;	systemctl --user daemon-reload
 ;
-; If that works, enable your service to start at boot:
+
-;	sudo systemctl enable my-service.service
+;	systemctl --user start my-service.service
 ;
 ; Check on the status of your service:
 ;	systemctl --user status my-service.service
-;	journalctl --follow --unit=my-service.service
+
-; which you can also abbreviate to:
+; If that works, enable your service to start automatically:
-;	journalctl -f -u my-service
+;	systemctl --user enable my-service.service
 ;
 ; Make sure the systemd user instance for the "debian" user is started at boot,
 ; otherwise your service(s) will only run when you're logged in:
 ;	sudo loginctl enable-linger debian
 ; (you only need to do this once)
 ;
 ;
 ; Follow log output related to your service (use control-C to exit):
 ;	journalctl -f --user-unit=my-service.service
 ;
 ;
-; For a list of special targets that may be useful as dependencies or
+
-; for ordering constraints, see:
+
-;	man systemd.special
+
 ;
 ; For directives available in the [Service] section of service units, see:
 ;	man systemd.service
 ;	man systemd.exec
 ;	man systemd.resource-control
 ;
 ; Note that comment lines can either start with ; or with #.  Using # is
 ; more common, but pastebin's syntax highlighting doesn't recognize # but
-Description=My system service
+
 
-; It may be necessary to include dependencies to prevent the script from
+
-; running too early during boot.
+
 
-; For example, if you need networking, you probably want:
+Description=My user service
-Wants=network-online.target
+
-After=network-online.target
+
 [Install]
-; If you need stuff in /dev, you probably want:
+
-Wants=systemd-udev-settle.service
+; When enabled, start service at startup
-After=systemd-udev-settle.service
+WantedBy=default.target
 
 
 [Service]
 
-; When enabled, start service at boot
+
-WantedBy=multi-user.target
+
 ;  or
 ;Type=exec
 ; The latter is better for diagnostics since if the program fails to start (e.g.
 ; the path in ExecStart is wrong) then with Type=exec the service will fail to
 ; start while with Type=simple the service will initially seem to start but then
 ; fail immediately afterwards.  However, Type=exec is unavailable in older versions
 ; of systemd (e.g. if you're still using debian stretch) and Type=simple is also
 ; slightly more efficient than Type=exec
 ;
 ; If your program instead just does some setup and then exits, use:
 ;Type=oneshot
 ; and in this case you probably also want to set:
 ;RemainAfterExit=yes
 ; (see the systemd.service man page for more details on these options)
 
-; By default the service runs as root, but you can choose a different user:
+; By default the service runs in ~, but you can choose a different working dir:
-User=debian
+;WorkingDirectory=~
 
-; By default the service runs in /, but you can choose a different working dir:
+
-WorkingDirectory=/home/debian
+