RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

# systemctl set-property systemd-user-sessions CPUAffinity=1

I'm trying to contain user(s) sessions in cgroup cpuset, I apologize if I get it wrong, way I understand to achieve this is though systemd-user-sessions + CPUAffinity, yet I get this when I tried above:

Unknown assignment CPUAffinity


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Setting CPUAffinity via systemctl set-property is not supported. If you *really* want to set it, you can set it directly in the service file. I'm not sure if it's a good idea, though.

I do that:

[Service]
CPUAccounting=1
CPUQuota=200%

as a Drop-In and it has NO effect, does not affect users shell sessions via ssh. (bug?)
How do I cgroup users' ssh-shell whole sessions. (except SU)
I was so easy with old libcgroup.

I see CPUQuota is not in RHEL's systemd 
but CPUAffinity also has no impact, and I tried both systemd-user-sessions and systemd-logind