Book Image

Linux Service Management Made Easy with systemd

4 (1)
Book Image

Linux Service Management Made Easy with systemd

4 (1)

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

Understanding journald on RHEL-type systems

There are a few big differences in how things are done in the Red Hat world. First, on your AlmaLinux machine, you'll see that there is no /var/log/journal/ directory, which means that journald log files will only be created in the /run/log/journal/ directory and will disappear every time you shut down or reboot the machine. If you want to change that, all you have to do is create that journal subdirectory, like this:

[donnie@localhost ~]$ sudo mkdir /var/log/journal

You'll immediately see that the journald log files are now persistent.

Note

Before you make the journald log files persistent on a production machine, evaluate whether or not you need to.

The other big difference is that on RHEL-type systems, journald and rsyslog work together, instead of independently. Instead of having both journald and rsyslog gather information from the rest of the operating system, only journald does. Then, rsyslog obtains the information...