Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Good catch @Patrick. I did the change you suggested, but still get these errors: Jun 12 19:15:52 intel-corei7-64 systemd[1]: /lib/systemd/system/memgoble.service: Unknown lvalue 'MemoryHigh' in section 'Service' Jun 12 19:15:52 intel-corei7-64 systemd[1]: /lib/systemd/system/memgoble.service: Unknown lvalue 'MemoryMax' in section 'Service' Which is strange because based on the systemd manual this is where the configuration should reside. Commented Jun 12, 2018 at 19:19
  • Check the man page on your system. Note the comments in the linked man page such as "MemoryMax= replaces MemoryLimit=" and others. The linked man page is the very latest version. Your system might not be running that version. Commented Jun 12, 2018 at 19:26
  • 2
    Yeap, the systemd version I thought I've had was actually much older, that was the problem. Commented Jun 12, 2018 at 20:03
  • 3
    PSA: This version mismatch issue is a very common source of confusion. Note that a hugely popular distro like RHEL 7 and basically all derivatives (CentOS 7, Amazon Linux 2, etc.) are still stuck on version 219! My personal favorite trick for exploring supported directives is to grep through the systemd.directives man page like this: man systemd.directives | grep -A 2 -i memory. For instance, that cmd tells me I can learn about MemoryLimit with man systemd.resource-control. Commented Apr 26, 2022 at 18:28