Managing
system services with systemd111
•
Multi-user mode•
Networked multiuser•
Graphical UI•
RebootEach of those runlevels allows a predefined set of services to be started/stopped when the runlevel is changed with init $runlevel. Of course, levels used to be based on each
other and were very simple, as outlined here Halt stopped all the services and then halted or powered off the system Single-user mode started a shell for one user Multi-user mode enabled regular login daemons on the virtual terminals Networked was like multi-user but with the network started Graphical was like networked but with graphical login via display manager (gdm or others Reboot was like halt, but at
the end of processing services, it issued a reboot instead of a halt.
These runlevels (and the default one when the system is booted) used to be defined in /etc/inittab, but the file placeholder reminds us of the following inittab is no longer used ADDING CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM Ctrl-Alt-Delete is handled by /usr/lib/systemd/system/ctrl- alt-del.target
#
# systemd uses 'targets' instead of runlevels. By default, there are two main targets multi-user.target: analogous to runlevel 3
# graphical.target: analogous to runlevel 5
#
#
To view current default target, run systemctl get-default
#
#
To set a default target, run systemctl set-default TARGET.target
So, by making this change to systemd, anew way to check the available boot targets and define them is in place.
Tools for Regular Operations112
We can find the available system targets by listing this folder:
Share with your friends: 
