Summary: | DOC: Setting MemoryLimit does not imply "MemoryAccounting=true" | ||
---|---|---|---|
Product: | systemd | Reporter: | Andy Melnikov <andy.melnikov> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Andy Melnikov
2014-05-15 12:20:30 UTC
Note that setting MemoryLimit= effectively turns on MemoryAccounting= but it won't show it with "systemctl show", since that actually shows the original MemoryAccounting= setting. Or in other words, there's a distinction between the MemoryAccounting= setting (which is unaffected by MemoryLimit=, as you experienced), and the actual memory accounting which is turned on in the kernel either by using MemoryAccounting= or by MemoryLimit=. If you follow wht I mean. Anyway, this is actually intended behaviour, but certainly something we could document better. Hence renaming the bug accordingly. We dropped the offending sentences now from the man page. Closing. See: https://github.com/systemd/systemd/pull/9669 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.