systemctl – inspect and manage systemd services
systemctl command helps you confirm system status and manage systemd services.
Show systemd Services
Simplest command is probably systemctl status:
● srv.ts.com
State: running
Jobs: 0 queued
Failed: 0 units
Since: Tue 2019-11-26 22:16:20 GMT; 1 months 18 days ago
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─[email protected]
│ │ └─init.scope
│ │ ├─2814 /lib/systemd/systemd –user
│ │ └─2815 (sd-pam)
│ ├─session-1365.scope
│ │ ├─591 sshd: greys [priv]
│ │ ├─601 sshd: greys@pts/0
│ │ ├─602 -bash
│ │ ├─607 systemctl status
│ │ └─608 pager
│ └─session-1290.scope
│ ├─2834 tmux
│ ├─2835 -bash
│ ├─2843 sudo -i
│ └─2844 -bash
├─init.scope
See Also
Linux Commands
Advanced Unix Commands
journalctl command
systemd reference
Make BIND9 named use only IPv4 (example of using systemctl status there)
See also
systemctl command helps you confirm system status and manage systemd services.
Show systemd Services
Simplest command is probably systemctl status:
● srv.ts.com
State: running
Jobs: 0 queued
Failed: 0 units
Since: Tue 2019-11-26 22:16:20 GMT; 1 months 18 days ago
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─[email protected]
│ │ └─init.scope
│ │ ├─2814 /lib/systemd/systemd –user
│ │ └─2815 (sd-pam)
│ ├─session-1365.scope
│ │ ├─591 sshd: greys [priv]
│ │ ├─601 sshd: greys@pts/0
│ │ ├─602 -bash
│ │ ├─607 systemctl status
│ │ └─608 pager
│ └─session-1290.scope
│ ├─2834 tmux
│ ├─2835 -bash
│ ├─2843 sudo -i
│ └─2844 -bash
├─init.scopeSee Also
Linux Commands Advanced Unix Commands journalctl command systemd reference Make BIND9 named use only IPv4 (example of using systemctl status there)
