Skip to content

DOCS-14846 non system user ulimit #5990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeff-allen-mongo merged 1 commit into from
Oct 13, 2021
Merged

DOCS-14846 non system user ulimit #5990

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions source/reference/ulimit.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,27 @@ change to system limits made using ``ulimit`` may revert following
a system restart. Check your distribution and operating
system documentation for more information.

You should typically start :binary:`~bin.mongod` using ``systemctl``,
which uses the ``ulimit`` settings:

.. code-block:: bash

systemctl start mongod.service

If you *do not* start :binary:`~bin.mongod` using ``systemctl``,
``systemd`` overrides some of the ``ulimit`` settings. For example, if
you start :binary:`~bin.mongod` as shown in the following command, then
a user slice (such as ``user-1000.slice``) ``systemd`` setting is used:

.. code-block:: bash

mongod --config ~/mongod.conf

.. note::

A ``systemd`` user slice limits the resources for the user's
processes.

macOS
`````

Expand Down