[DOCS-1031] Document Ulimit Settings in Config file Created: 22/Jan/13 Updated: 23/Jan/13 Resolved: 23/Jan/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 4 weeks, 1 day ago |
| Description |
|
Ulimit documentation does not cover how to set limits in the /etc/security/limits.conf file. We need to cover this as RHEL and its fork's all use this file to manipulate limits rather than the ulimit command.
Additionally, you also need to set the following in /etc/pam.d/login
|
| Comments |
| Comment by Sam Kleinman (Inactive) [ 23/Jan/13 ] |
|
I don't think its appropriate or productive to document operation system and distribution specific administrative processes in the MongoDB documentation. We mention that you can/should find a way to make ulimit settings persistent, but the method can depend on facts of your deployment that will be hard for us to predict, and may have side effects that are difficult for us to predict. Furthermore each operating system handles these kinds of configurations slightly differently, and configuration methods can change between versions of a single distribution. Regardless, this kind of information can and should be documented by the operating system vendor. |