Initial Settings : Services2019/07/10 |
| [1] | It's possible to make sure services' status like follows. |
|
# display the list of services which are running root@dlp:~# systemctl -t service UNIT LOAD ACTIVE SUB DESCRIPTION apparmor.service loaded active exited Load AppArmor profiles blk-availability.service loaded active exited Availability of block devices console-setup.service loaded active exited Set console font and keymap cron.service loaded active running Regular background program processing daemon dbus.service loaded active running D-Bus System Message Bus ..... ..... systemd-udevd.service loaded active running udev Kernel Device Manager systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown systemd-user-sessions.service loaded active exited Permit User Sessions user-runtime-dir@0.service loaded active exited User Runtime Directory /run/user/0 user@0.service loaded active running User Manager for UID 0 LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 33 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. # the list of all services' setting root@dlp:~# systemctl list-unit-files -t service UNIT FILE STATE apparmor.service enabled apt-daily-upgrade.service static apt-daily.service static autovt@.service enabled blk-availability.service enabled ..... ..... umountnfs.service masked umountroot.service masked urandom.service static user-runtime-dir@.service static user@.service static x11-common.service masked 133 unit files listed. |
| [2] | Stop and turn OFF auto-start setting for a service if you don'd need it. (it's [Apparmor] as an example below) |
|
root@dlp:~# systemctl stop apparmor root@dlp:~# systemctl disable apparmor |
| Sponsored Link |