DOCSP-35407 Document usage of MONGODB_CONFIG_OVERRIDE_NOFORK (#6445)

* DOCSP-35407 Document usage of MONGODB_CONFIG_OVERRIDE_NOFORK

* DOCSP-35407 updates for AQ's feedback

.gitignore

@@ -85,4 +85,6 @@ primer/source/includes/table-linux-kernel-version-production.yaml
 venv
 .vscode
 changelogs/.mongodb-jira.yaml
-source/includes/qe-tutorials/csharp/obj/
+source/includes/qe-tutorials/csharp/obj/
+source/includes/sdk/go/markdown/
+source/includes/mongosql/markdown/

source/reference/configuration-options.txt

@@ -78,7 +78,8 @@ settings that you may adapt to your local configuration:
 
 The Linux package init scripts included in the official MongoDB packages depend
 on specific values for :setting:`systemLog.path`, :setting:`storage.dbPath`, and
-:setting:`processManagement.fork`. If you modify these settings in the default
+:setting:`processManagement.fork` or ``MONGODB_CONFIG_OVERRIDE_NOFORK``
+system environment variable. If you modify these settings in the default 
 configuration file, :binary:`~bin.mongod` may not start.
 
 .. [#yaml-json] YAML is a superset of :term:`JSON`.
@@ -915,6 +916,14 @@ Core Options
    The :setting:`processManagement.fork` option is not supported on Windows.
 
    .. include:: /includes/extracts/linux-config-expectations-processmanagement-fork.rst
+
+   .. note:: 
+
+      Alternatively, you can set the ``MONGODB_CONFIG_OVERRIDE_NOFORK``
+      environment variable on your system to ``true`` to run the
+      :binary:`~bin.mongos` or :binary:`~bin.mongod` process in the 
+      background. If you set the environment variable, it overrides the
+      setting for ``processManagement.fork``. 
 
 
 .. setting:: processManagement.pidFilePath