mirror of
https://github.com/systemd/systemd
synced 2024-10-14 20:17:52 +00:00
Merge pull request #28679 from keszybz/two-new-news-tweaks
Two news tweaks
This commit is contained in:
commit
7f878268ff
14
NEWS
14
NEWS
|
@ -113,10 +113,12 @@ CHANGES WITH 254:
|
|||
|
||||
Service Manager:
|
||||
|
||||
* "Startup" memory settings are now supported. Previously IO and CPU
|
||||
settings were already supported via StartupCPUWeight= and similar.
|
||||
The same logic has been added for the various per-unit memory
|
||||
settings StartupMemoryMax= and related.
|
||||
* Memory limits that apply while the unit is activating are now
|
||||
supported. Previously IO and CPU settings were already supported via
|
||||
StartupCPUWeight= and similar. The same logic has been added for the
|
||||
various manager and unit memory settings (DefaultStartupMemoryLow=,
|
||||
StartupMemoryLow=, StartupMemoryHigh=, StartupMemoryMax=,
|
||||
StartupMemorySwapMax=, StartupMemoryZSwapMax=).
|
||||
|
||||
* The service manager gained support for enqueuing POSIX signals to
|
||||
services that carry an additional integer value, exposing the
|
||||
|
@ -700,8 +702,8 @@ CHANGES WITH 254:
|
|||
server-side environment variable expansion in specified command
|
||||
lines. Expansion defaults to enabled for all execution types except
|
||||
--scope, where it defaults to off (and prints a warning) for backward
|
||||
compatibility reasons. --scope will be flipped to default enabled too
|
||||
in a future release, so if you are using --scope and passing a '$'
|
||||
compatibility reasons. --scope will be flipped to enabled by default
|
||||
too in a future release. If you are using --scope and passing a '$'
|
||||
character in the payload you should start explicitly using
|
||||
--expand-environment=yes/no according to the use case.
|
||||
|
||||
|
|
Loading…
Reference in a new issue