On Do, 10.05.18 15:01, john terragon (terragonj...@yahoo.com) wrote:
>
> On Wednesday, May 9, 2018, 10:02:14 PM GMT+2, Simon McVittie
> wrote:
>
> >I don't think this is supported. systemd behaves as though cgroups v2 is
> >in use (single unified cgroup hierarchy) even
On Mi, 09.05.18 21:01, Simon McVittie (s...@collabora.com) wrote:
> On Wed, 09 May 2018 at 16:46:09 +, john terragon wrote:
> > I have the memory cgroup controller configured in the kernel. I want to use
> > it
> > myself directly without interference from systemd.
>
> I don't think this is
On Mi, 09.05.18 16:46, john terragon (terragonj...@yahoo.com) wrote:
> Hi.
>
> I have the memory cgroup controller configured in the kernel. I want
> to use it myself directly without interference from systemd. I tried
> setting DefaultMemoryAccounting=no in system.conf but systemd seems
> to
On Wednesday, May 9, 2018, 10:02:14 PM GMT+2, Simon McVittie
wrote:
>I don't think this is supported. systemd behaves as though cgroups v2 is
>in use (single unified cgroup hierarchy) even if you are currently using
>cgroups v1 (one parallel hierarchy per controller).
On Wed, 09 May 2018 at 16:46:09 +, john terragon wrote:
> I have the memory cgroup controller configured in the kernel. I want to use it
> myself directly without interference from systemd.
I don't think this is supported. systemd behaves as though cgroups v2 is
in use (single unified cgroup
Hi.
I have the memory cgroup controller configured in the kernel. I want to use it
myself directly without interference from systemd. I tried setting
DefaultMemoryAccounting=no in system.conf but systemd seems to still interfere
with the hierarchy for the memory controller (e.g. systemctl