Systemd, a controversial system and service manager for Linux operating systems, has a major version release as Systemd 247.
Speaking of new changes, systemd 247 has added a new service called systemd-oomd to monitor and take action on processes when memory or swap goes above the configured limits.
Additionally, it also has a new helper oomctl to introspect systemd-oomd state. However, systemd-oomd service is only enabled by default in developer mode and hence still an experimental addition in this release.
As Linux distributions are switching to Btrfs as default filesystem like the latest Fedora 33, systemd-homed in v247 now uses the Btrfs file system by default (if available) while creating home directories in LUKS volumes.
Furthermore, systemd-homed also now maintains a “dirty” flag for each LUKS encrypted home directory. The flag indicates that a home directory has not been deactivated cleanly when offline.
Among the other enhancements, here’s what systemd 247 includes:
- Support for “recovery keys” in JSON user records managed by systemd-homed
- Systemd-cryptsetup gained support for processing detached LUKS headers specified on the kernel command line
- Bootctl’s set-default and set-oneshot commands now accept the three special strings “@default”, “@oneshot”, “@current” in place of a boot entry id
- Added a new “credentials” logic to system services to pass privileged data to services in a safe and secure way
- Systemd-detect-virt now recognize IBM PowerVM machine virtualization
- The cgroup2 file system is now mounted with the “memory_recursiveprot” mount option
- “systemd-dissect” tool to inspect OS disk images moved from
- With systemd-udevd 247, udev tags assigned to a device get removed only if the device is unplugged
For complete details about changes in systemd 247, read the NEWS file.
Via — Phoronix