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

Understanding timer options

The best way to start explaining the timer options is to look at some examples of timers that are already on our systems. We'll begin by looking at a timer on the Alma Linux machine.

Understanding monotonic timers

There are two ways to specify the time at which you want a service to automatically run. In this section, we'll look at the monotonic method. This means that instead of configuring the job to run at a specific calendar and clock time, you'll instead configure the job to run after some sort of event that serves as a starting point. A starting point can be system bootup, timer activation, the time since a timer's associated service last ran, or any of several other things (you can see all of the monotonic starting points by looking at the systemd.timer man page). For an example of a monotonic timer, let's look at dnf-makecache.timer on the Alma Linux machine.

Red Hat-type operating systems, such as Alma Linux, use...