|
- System and Service Manager
System and Service Manager systemd is a suite of basic building blocks for a Linux system It provides a system and service manager that runs as PID 1 and starts the rest of the system
- Frequently Asked Questions - systemd
A: By default, systemd places all systemd daemons in their own cgroup in the “cpu” hierarchy Unfortunately, due to a kernel limitation, this has the effect of disallowing RT entirely for the service
- New Control Group Interfaces - systemd
Systemd provides three unit types that are useful for the purpose of resource control: Services encapsulate a number of processes that are started and stopped by systemd based on configuration
- systemd-boot UEFI Boot Manager
systemd-boot reads simple and entirely generic boot loader configuration files; one file per boot loader entry to select from All files need to reside on the ESP
- Writing syslog Daemons Which Cooperate Nicely With systemd
A few notes in advance: systemd centralizes all log streams in the Journal daemon Messages coming in via dev log, via the native protocol, via STDOUT STDERR of all services and via the kernel are received in the journal daemon
- systemd Repository Architecture
Most of those tests should be able to run via systemd-nspawn, which is orders-of-magnitude faster than qemu, but some tests require privileged operations like using dm-crypt or loopdev
- Running Services After the Network Is Up - systemd
Its primary purpose is for ordering things properly at shutdown: since the shutdown ordering of units in systemd is the reverse of the startup ordering, any unit that has After=network target can be sure that it is stopped before the network is shut down when the system is going down
- Mount Requirements - systemd
This document describes the requirements placed by systemd on the time when various parts of the file system hierarchy must be available and mounted during boot
|
|
|