Re: Relationship between cgroup hierarchy and slice names

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Do, 05.05.22 10:44, Yeongjin Kwon (yeongjinkwon@xxxxxxxxx) wrote:

> On Wed, May 4, 2022 at 4:03 AM Lennart Poettering
> <lennart@xxxxxxxxxxxxxx> wrote:
> >
> > The slice names match 1:1 to the position in the cgroup tree, that's
> > where they were designed.
> >
> > Basically our rule is: if the object unit types encapsulates
> > already have a file system path as name then we don't allow you to
> > make up a new name, but insist that the unit name is derived from that
> > pre-existing file system path.
>
> I see, thank you for responding.
>
> Then would it be possible to somehow override the "Slice" property for
> all units underneath the slice so that it points to another, custom
> created slice? Maybe using some conditional overriding mechanism?

You can override the slice for any non-slice unit that is backed by a
cgroup via a dropin that overrides Slice=.

But maybe I don#t grok your question.

Lennart

--
Lennart Poettering, Berlin



[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux