Hey, now look at you, the end of another module.
How good do you feel?
Really, tell me, how good do you feel?
You've been through a section where we've been looking at Linux services,
and if you've worked through all of the demonstrations
along with me on your own systems,
you are now going to be at the precipice of some enormous success,
be it in your certification exams for CompTIA,
or be it in your career.
The more you put into the effort running through these videos,
the more you're going to get back.
Now we've been looking at systemd.
Most modern Linux systems will have systemd,
along with the ecosystem of managing our services with systemcl,
managing our time and date systems with timedatectl,
and the localectl command,
where we've seen we can go through and manage some of our locale settings.
We saw extending from what we had looked at with our loop devices,
by using service units,
we can script the creation of our loop devices and reading of
the partition table during the boot phase.
Timer units can help us replace some of the scheduling
utilities that we might have previously run.
So with timer units, generally,
software vendors are going to be adding these along with their software,
such as we saw with sysstat,
where we could see that we were collecting
performance information every 10 minutes.
Our common services included the traditional cron and at daemons.
These have been traditionally used in Linux for many years,
where we've gone through then to schedule our tasks.
However, we might still see them for users creating their own cron jobs; however,
we might see more of a movement towards systemd timer units,
so we don't need these services running in the background.
Our time service traditionally is going to be chrony,
but chrony will act as both a time server and a time client.
If we only need a time client,
we might consider using the systemd and timesync daemon as a replacement,
so it uses less resource and less exposure to network attacks.
Process management is all about looking at our running processes,
and this can include the command top, as well as the individual commands,
such as ps for our process status, pstree,
where we can see the whole hierarchy from the process ID 1 systemd down.
We can search for processes with pgrep, and we can terminate those processes
if required using the pkill command. To set up the process priority, we can
use the nice command, and using the renice command,
we can change the priority of our running processes. So there's a lot
for you to understand and to work through within this module, but
certainly you can go through and watch it again.
But the biggest thing is to watch and follow through the
demonstrations on your own systems. But if you're ready to move
on to the next module, we're going to have some fun looking at managing the Linux boot process.