It Looks Like Systemd 231 Will Soon Be Released, Adds MemoryDenyWriteExecute
It's been a while since the last systemd release (230 in May) while it looks like the systemd 231 release is imminent.
Over the past day, systemd developers have begun updating the NEWS entry for the v231 milestone. The systemd 231 release hasn't happened quite yet, but here's a look at some of the functionality that's coming.
Systemd 231 will allow the MemoryLimit and TasksMax and related unit settings to be specified as a percentage, support for the "memory" cgroup controller on cgroupsv2, a new MemoryDenyWriteExecute (optional) setting to prevent a service from creating memory mappings that are writable and executable at the same time (great for security!), systemd-resolved improvements, various other network-related systemd additions, support for VERSION_CODENAME in the os-release file, and many other changes.
Those wanting to dig through the systemd Git for an early look at the v231 changes can do so via systemd on GitHub.
Over the past day, systemd developers have begun updating the NEWS entry for the v231 milestone. The systemd 231 release hasn't happened quite yet, but here's a look at some of the functionality that's coming.
Systemd 231 will allow the MemoryLimit and TasksMax and related unit settings to be specified as a percentage, support for the "memory" cgroup controller on cgroupsv2, a new MemoryDenyWriteExecute (optional) setting to prevent a service from creating memory mappings that are writable and executable at the same time (great for security!), systemd-resolved improvements, various other network-related systemd additions, support for VERSION_CODENAME in the os-release file, and many other changes.
Those wanting to dig through the systemd Git for an early look at the v231 changes can do so via systemd on GitHub.
62 Comments