Book Image

Linux Service Management Made Easy with systemd

4.5 (2)
Book Image

Linux Service Management Made Easy with systemd

4.5 (2)

Overview of this book

Linux Service Management Made Easy with systemd will provide you with an in-depth understanding of systemd, so that you can set up your servers securely and efficiently.This is a comprehensive guide for Linux administrators that will help you get the best of systemd, starting with an explanation of the fundamentals of systemd management.You’ll also learn how to edit and create your own systemd units, which will be particularly helpful if you need to create custom services or timers and add features or security to an existing service. Next, you'll find out how to analyze and fix boot-up challenges and set system parameters. An overview of cgroups that'll help you control system resource usage for both processes and users will also be covered, alongside a practical demonstration on how cgroups are structured, spotting the differences between cgroups Version 1 and 2, and how to set resource limits on both. Finally, you'll learn about the systemd way of performing time-keeping, networking, logging, and login management. You'll discover how to configure servers accurately and gather system information to analyze system security and performance. By the end of this Linux book, you’ll be able to efficiently manage all aspects of a server running the systemd init system.
Table of Contents (23 chapters)
1
Section 1: Using systemd
12
Section 2: Understanding cgroups
16
Section 3: Logging, Timekeeping, Networking, and Booting

Summary

In this chapter, we've learned a lot about cgroup Version 2. We started with a discussion about the deficiencies in cgroups Version 1, and how cgroup Version 2 is better. Then, we looked at how to allow non-privileged users to set resource limits on their containers, and how to use the cpuset resource controller. Finally, we took a brief look at how to convert a RHEL 8-type machine to use cgroup Version 2.

Once again, I'm reading your mind, and you're wondering why cgroup Version 2 hasn't yet been universally adopted if it's so good. Well, it's just that certain critical programs and services, especially containerization services, are still hardcoded to use Version 1. Fortunately, the situation is improving, and it's a safe bet that Version 2 will become the standard within our lifetimes.

All right, this concludes Part 2 of this tome. Let's start Part 3 with a discussion of journald. I'll see you there.