-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
RH442 - RHEL 8 1 20190828
-
None
-
False
-
-
False
-
5
-
-
-
en-US (English)
Please fill in the following information:
URL: | ch05s05 |
Reporter RHNID: | carias@redhat.com |
Section title: | Lab: Managing Resource Limits with Control Groups |
Language: | English |
Issue description
The exercise expect students to use LimitNPROC to limit number of processes for a given service. While the version of systemd on RHEL 8 doesn't explicitly state this in the systemd.exec(5) man page, this is a snippet out of a more modern systemd man page:
'Note that LimitNPROC= will limit the number of processes from one
(real) UID and not the number of processes started (forked) by the
service. Therefore the limit is cumulative for all processes
running under the same UID. Please also note that the LimitNPROC=
will not be enforced if the service is running as root (and not
dropping privileges). Due to these limitations, TasksMax= (see
systemd.resource-control(5)) is typically a better choice than LimitNPROC=.'
https://manpages.debian.org/bookworm/systemd/systemd.exec.5.en.html
The reason why I mention this is that if student used TasksMax (which is also the correct solution on RHEL 8) it automatically failed grading because it seems like the grading script checks configuration files rather than the desired outcome, i.e. that a service cannot fork more processes than the limit enforced by TasksMax
Steps to reproduce:
Workaround:
Expected result: