From 7499da9a1790e4093284ff890eee439294ba3d29 Mon Sep 17 00:00:00 2001 From: Benoit Chesneau Date: Fri, 27 Feb 2026 15:16:40 +0100 Subject: [PATCH] docs: regenerate settings.md for control_socket default --- docs/content/reference/settings.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/content/reference/settings.md b/docs/content/reference/settings.md index bd9aaa3f..05fc2f9c 100644 --- a/docs/content/reference/settings.md +++ b/docs/content/reference/settings.md @@ -54,7 +54,7 @@ A WSGI application path in pattern ``$(MODULE_NAME):$(VARIABLE_NAME)``. **Command line:** `--control-socket PATH` -**Default:** `'gunicorn.ctl'` +**Default:** `'/run/gunicorn.ctl'` Unix socket path for control interface. @@ -62,8 +62,9 @@ The control socket allows runtime management of Gunicorn via the ``gunicornc`` command-line tool. Commands include viewing worker status, adjusting worker count, and graceful reload/shutdown. -By default, creates ``gunicorn.ctl`` in the working directory. -Set an absolute path for a fixed location (e.g., ``/var/run/gunicorn.ctl``). +By default, creates ``/run/gunicorn.ctl`` (requires write access to +``/run``). For user-level deployments, specify a different path such +as ``/tmp/gunicorn.ctl`` or ``~/.gunicorn.ctl``. Use ``--no-control-socket`` to disable.