From: Dominick Grift <dominick.grift@defensec.nl>
To: Russell Coker <russell@coker.com.au>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: cgroups
Date: Thu, 04 Mar 2021 17:47:32 +0100 [thread overview]
Message-ID: <ypjl1rcun9wb.fsf@defensec.nl> (raw)
In-Reply-To: <201858869.AyTo3W3VYL@liv> (Russell Coker's message of "Thu, 04 Mar 2021 22:21:44 +1100")
Russell Coker <russell@coker.com.au> writes:
> https://sourceforge.net/projects/libcg/files/
>
> Above seems to be the source for the programs listed in policy/modules/
> services/cgroup.fc, upstream has no changes since 2014 and the package in
> Debian doesn't support cgroup2 so is pretty much useless.
>
> Is there any reason for not deleting policy/modules/services/cgroup.* from
> refpolicy?
libgroup is indeed probably history. Although I vaguely recall it still
being used somewhere out there. I wouldnt mind removing it.
>
> Also as an aside what is the best way of managing cgroups and do we have
> policy that works with it?
I suppose depends who you ask. Many nowayday's will probably say that systemd
should be the only cgroup manager.
On systems with systemd i generally use systemd, one my openwrt powered
router i just use shell and (init)?scripts
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift
prev parent reply other threads:[~2021-03-04 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 11:21 cgroups Russell Coker
2021-03-04 16:18 ` cgroups Chris PeBenito
2021-03-04 16:47 ` Dominick Grift [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ypjl1rcun9wb.fsf@defensec.nl \
--to=dominick.grift@defensec.nl \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).