Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

[virgo]

>  On Tue, May 12, 2020 at 12:47:51PM +0000, virgo wrote:
>  ...
>  
>   > I recommend you to ask the question about v2 support on Fedora
>  
>  Bugzilla for=
>  
>   >  the
>   > 
>   > libcgroup package
>   > <https://bugzilla.redhat.com/buglist.cgi?classification=3DFedora&compo...
>   > =3Dlibcgroup&product=3DFedora&query_format=3Dadvanced>.
>   
>   Prior to the top post, I went through the Bugzilla tickets, with these
>   parameters:
>   
>   * component=libcgroup
>   * order=changeddate DESC
>   * product=Fedora
>   * query_format=advanced
>   
>   and the hits dating back to 2015[fn:1] were just a dozen, none making
>   mention
>   of v2. So, I am not sure whether opening feature requests would help.
>  
>  Fedora uses systemd that enforces cgroup v2. If libcgroup package is not
>  compatible with cgroup v2, then libcgroup package is not compatible with
>  Fedora and this is a bug and should be reported to the Fedora's Bugzilla.
>  
>  ...
>  
>   By the way, what would you and (and others) recommend as a
>  
>  replacement for
>  
>   libcgroup-tools?[fn:2]
>  
>  No idea. I don't use cgroups for anything on purpose. As far as I know,
>  cgroups membership in Fedora is defined by systemd's logind. Whether it
>  suits
>  your needs, I have no idea. I also think it's possible to manage the
>  membership manually by editing files in cgroup2 pseudo file system. 
Duly noted,
thank you for your time.
> 
> -- Petr

Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

[Samuel Sieb]

Please fix your email client.  Every reply you send starts a new thread.
Are you actually using the Pandora email client?  It's still being 
developed?  Unfortunately, it appears to not create any of the proper 
headers.

On 5/12/20 7:09 AM, virgo wrote: