From: baltakatei Date: Mon, 27 Apr 2020 16:43:38 +0000 (-0700) Subject: feat(doc): Add example systemctl status messages X-Git-Tag: 0.1.0~22 X-Git-Url: https://zdv2.bktei.com/gitweb/BK-2020-03.git/commitdiff_plain/7168745037943e150d454c6d9e8871c6b97349dc?ds=sidebyside feat(doc): Add example systemctl status messages Add example messages returned to user after running the `systemctl` commands to enable and start a system service. Commands were added from a virtual image of Debian 10 after following the instruction steps. --- diff --git a/config-shared/syncthing/INSTRUCTIONS.md b/config-shared/syncthing/INSTRUCTIONS.md index dd68fb7..c63cd7d 100644 --- a/config-shared/syncthing/INSTRUCTIONS.md +++ b/config-shared/syncthing/INSTRUCTIONS.md @@ -51,12 +51,30 @@ The commands to create a `systemd` system service under user `baltakatei` are: $ sudo systemctl enable syncthing@baltakatei.service - $ sudo systemctl start syncthing@baltakatei.service + $ sudo systemctl start syncthing@baltakatei.service + +The following notifications may appear while running these commands: + + $ systemctl enable syncthing@baltakatei.service + Created symlink /etc/systemd/system/multi-user.target.wants/syncthing@baltakatei.service → /lib/systemd/system/syncthing@.service. The status of the new system service can be verified via: $ systemctl status syncthing@baltakatei.service +The resulting status data will resemble: + + $ systemctl status syncthing@baltakatei.service + ● syncthing@baltakatei.service - Syncthing - Open Source Continuous File Synchronization for baltakatei + Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor preset: enabled) + Active: active (running) since Mon 2020-04-27 09:01:00 PDT; 3min 34s ago + Docs: man:syncthing(1) + Main PID: 2799 (syncthing) + Tasks: 23 (limit: 1132) + Memory: 45.3M + CGroup: /system.slice/system-syncthing.slice/syncthing@baltakatei.service + └─2799 /usr/bin/syncthing -no-browser -no-restart -logflags=0 + #### 2.2.b. Enable automatic startup via `systemd` upon login (user service). For a user service, identify which user under which to run