Enhance logging when DefaultTasksMax is hit
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
Submission type
- Request for enhancement (RFE)
systemd version the issue has been seen with
systemd-228-25.3.1.x86_64
Used distribution
openSUSE Leap 42.2
We currently had problems in a system running against the TasksMax border. We are a producer of a complex server system operating in Java based on Linux. We understand the need for introducing limits for security and we also understand it is cumbersome to discuss the defaults of these limits. However what us strikes is the fact it was quite hard to find the underlying reason for this. In dmesg and journalctl there is a statement like cgroup: fork rejected by pids controller in /system.slice/xxx.service. From our point of view it would be nice to have a more fine grained message that the tasks limit is hit. Especially because this limit is quite new beside of ulimit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the pids controller rejection reported through dmesg and journalctl, with attention to DefaultTasksMax and the affected system.slice service. The work is complete when hitting the tasks limit produces a more fine-grained message that distinguishes this limit from other fork or ulimit failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100