#3252 RFE: Support for user limits via cgroups
Closed: wontfix 4 years ago by pbrezina. Opened 7 years ago by ondrejv2.

It would be nice if we could define user session limits (for CPU and memory for start) via CGroup handlers.
Scenario:
1. we define ldap schema to store these extra attributes for users
2. pam_sss would cooperate with systemd and define cpu/memory limits on user control group slice.

Does it make a sense?


It makes sense to cooperate with systemd on this one. See for example: https://lists.freedesktop.org/archives/systemd-devel/2015-September/034097.html here Lennart talks about an API to query which would allow logind to query which slice a user belogs to.

I think it would make sense to look into this ticket when the files provider is ready and when the D-Bus interface allows querying additional attributes for users regardless of whether they come from LDAP or files. Then the cgroups "interface" could be part of sssd-dbus.

Of course, the schema is a whole another question..

Fields changed

milestone: NEEDS_TRIAGE => SSSD Patches welcome

Fields changed

rhbz: => todo

Metadata Update from @ondrejv2:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4285

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata