Systemd – Running CentOS 7 in different modes using systemd targets

What are targets?

You can configure your CentOS system to run in different modes. For example you can run your system in graphical mode, if you want to use it as desktop workstation. Or you can run your system in command line mode, if you are interested in using your systems bash terminal. You can control which mode to run in using systemd targets.

A target is basically a grouping of resources that you want started/activated when your system is booting up. These resources are called units in systemd. There are different types of units, and you can list the different types by running:

$ systemctl -t help
Available unit types:
service
socket
busname
target
snapshot
device
mount
automount
swap
timer
path
slice
scope   

Notice that targets themselves are a type of unit. The ‘service’ and ‘target’ units are the main unit types that you’re likely to spend most of your time working with. Each unit is represented in the form of a file, these files are found in the /usr/lib/systemd/system. These unit files names have a suffix that relates to the type of unit they are. For example to list all target units, we do:

$ ls -l /usr/lib/systemd/system | grep "target$"
-rw-r--r--. 1 root root  312 Jul  2  2014 anaconda.target
-rw-r--r--. 1 root root  546 Jun 10  2014 basic.target
-rw-r--r--. 1 root root  379 Jun 10  2014 bluetooth.target
-rw-r--r--. 1 root root  366 Jun 10  2014 cryptsetup.target
lrwxrwxrwx. 1 root root   13 Mar 14 19:16 ctrl-alt-del.target -> reboot.target
lrwxrwxrwx. 1 root root   16 Mar 14 19:16 default.target -> graphical.target
-rw-r--r--. 1 root root  431 Jun 10  2014 emergency.target
-rw-r--r--. 1 root root  440 Jun 10  2014 final.target
-rw-r--r--. 1 root root  460 Jun 10  2014 getty.target
-rw-r--r--. 1 root root  522 Jun 10  2014 graphical.target
.
.
.
...etc.

Another way to list all target units is by using the systemctl command:

$ systemctl list-unit-files --type=target
UNIT FILE                  STATE
anaconda.target            static
basic.target               static
bluetooth.target           static
cryptsetup-pre.target      static
cryptsetup.target          static
.
.
...etc  

To see which targets are currently active, we do:

$ systemctl list-units --type target
UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
basic.target          loaded active active Basic System
cryptsetup.target     loaded active active Encrypted Volumes
getty.target          loaded active active Login Prompts
local-fs-pre.target   loaded active active Local File Systems (Pre)
local-fs.target       loaded active active Local File Systems
multi-user.target     loaded active active Multi-User System
network-online.target loaded active active Network is Online
network-pre.target    loaded active active Network (Pre)
network.target        loaded active active Network
nfs-client.target     loaded active active NFS client services
paths.target          loaded active active Paths
remote-fs-pre.target  loaded active active Remote File Systems (Pre)
remote-fs.target      loaded active active Remote File Systems
slices.target         loaded active active Slices
sockets.target        loaded active active Sockets
sound.target          loaded active active Sound Card
swap.target           loaded active active Swap
sysinit.target        loaded active active System Initialization
timers.target         loaded active active Timers

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.

19 loaded units listed. Pass --all to see loaded but inactive units, too.

As you can see, you can have multiple targets that are active at any one time, since a target is just a collection of other units (which can also include other target units). If a target is active, then it means that all the units that is part of that target group are enabled/running/active. You can view a list of all units for a given target (e.g. multi-user.target) using the systemctl command:

$ systemctl list-dependencies multi-user.target
multi-user.target
● ├─abrt-ccpp.service
● ├─ModemManager.service
● ├─systemd-user-sessions.service
● ├─tuned.service
● ├─vboxadd-service.service
● ├─vboxadd.service
● ├─vmtoolsd.service
● ├─basic.target
● │ ├─alsa-restore.service
● │ ├─alsa-state.service
● │ ├─microcode.service
● │ ├─rhel-autorelabel-mark.service
● │ ├─rhel-autorelabel.service
● │ ├─rhel-configure.service
● │ ├─rhel-dmesg.service
● │ ├─rhel-loadmodules.service
● │ ├─selinux-policy-migrate-local-changes@targeted.service
● │ ├─paths.target
● │ ├─slices.target
● │ │ ├─-.slice
● │ │ └─system.slice
● │ ├─sockets.target
● │ │ ├─avahi-daemon.socket
● │ │ ├─cups.socket
● │ │ ├─dbus.socket
● │ │ ├─dm-event.socket
● │ │ ├─virtlockd.socket
● │ │ └─virtlogd.socket
● │ ├─sysinit.target
● │ │ ├─dev-hugepages.mount
● │ │ ├─dev-mqueue.mount
● │ │ ├─dmraid-activation.service
.
.
...etc

Notice that a target can also include other targets. In fact the targets have a pyramid like structure, i.e. the top most target activates other targets, which in turn call on further targets.

The Default target

Due to the pyramid structure of targets, it means that there is a single target at the very top of the pyramid. The top most target that gets started during boot time is called the default target. You can view what the default target is by running:

$ systemctl get-default
graphical.target

In this example, it means that this target will start up the GNOME desktop gui interface during boot time. You can change the default target like this:

$ systemctl set-default multi-user.target
rm '/etc/systemd/system/default.target'
ln -s '/usr/lib/systemd/system/multi-user.target' '/etc/systemd/system/default.target'

$ systemctl get-default
multi-user.target

Notice that changing the default target is just a case of updating the “default.target” symbolic link behind the scenes.

Commonly used targets

The most commonly used targets (in terms of operational mode) are those that are as follows:

• multi-user.target – Fully operational mode, this is the normal mode but without Gnome desktop UI.
• graphical.target – Same as multi-user.target but with the Gnome desktop UI enabled.
• rescue.target – this enters troubleshooting mode. A bit like single user mode I think.
• emergency.target – this is more minimal version of the rescue.target.

Switching betweeen top-level targets

There’s a few ways to switch between top-level targets. First ways to do this:

• Change the default target, and then reboot the machine.
• Use systemctl’s “isolate” subcommand (this is non-persistant)
• From the grub menu, hit e, then specify the target (this is non-persistant)

Switching targets using the “isolate” subcommand

We can switch using the isolate subcommand. The isolate subcommand can only be used with a select few targets:

$ grep -ir 'AllowIsolate=yes' /usr/lib/systemd/system
/usr/lib/systemd/system/multi-user.target:AllowIsolate=yes
/usr/lib/systemd/system/reboot.target:AllowIsolate=yes
/usr/lib/systemd/system/poweroff.target:AllowIsolate=yes
/usr/lib/systemd/system/rescue.target:AllowIsolate=yes
/usr/lib/systemd/system/emergency.target:AllowIsolate=yes
/usr/lib/systemd/system/graphical.target:AllowIsolate=yes
/usr/lib/systemd/system/halt.target:AllowIsolate=yes
/usr/lib/systemd/system/initrd-switch-root.service:AllowIsolate=yes
/usr/lib/systemd/system/initrd-switch-root.target:AllowIsolate=yes
/usr/lib/systemd/system/initrd.target:AllowIsolate=yes
/usr/lib/systemd/system/kexec.target:AllowIsolate=yes
/usr/lib/systemd/system/system-update.target:AllowIsolate=yes
/usr/lib/systemd/system/anaconda.target:AllowIsolate=yes

This list includes the 4 commonly used targets.

So we use the isolate command like this:

:

$ systemctl isolate rescue.target

You can then check that you are in rescue.target state like this:

Notice that we only have a small number of targets active, since we are in rescue mode. Even sshd service is disabled.

We can return back to mult-user.target using the isolate subcommand again:

$ systemctl isolate multi-user.target

By the way, emergency.target looks like this:

Note: due to emergency mode being barebones. You can’t use isolate to switch to another target while being in emergency.target state. So the only way out of the emergency mode is to reboot the system.

Switching targets via the grub menu

This is something that you will commonly do if for some reason you have trouble booting up into graphical or mult-user targets. In which you can use grub to boot into a trouble shooting mode, such as rescue.target or emergency.target. While your machine is booting, as soon as you see the grub menu, select the (e)dit option:

Then navigate to the line that starts with “linux16”, and go to the end of the line, and then append the following setting:

systemd.unit=rescue.target

So that we have:

Then control+x to resume the boot process with the modified settings.

In this example we have gone into the rescue.target, this means that after that has been done, you can use systemctl’s isolate command to return to one of the fully operational normal targets, mult-user or graphical.

[post-content post_name=rhsca-quiz]