Skip to content

Update runtime-control.md #421

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.

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
merged 3 commits into from
Apr 17, 2025
Merged
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
description: Understand the NGINX processes that handle traffic, and how to control
them at runtime.
docs: DOCS-379
title: Controlling NGINX Processes at Runtime
title: Control NGINX Processes at Runtime
toc: true
weight: 100
type:
Expand Down Expand Up @@ -36,4 +36,4 @@ where `<SIGNAL>` can be one of the following:

The `kill` utility can also be used to send a signal directly to the master process. The process ID of the master process is written, by default, to the **nginx.pid** file, which is located in the **/usr/local/nginx/logs** or **/var/run** directory.

For more information about advanced signals (for performing live binary upgrades, for example), see [Controlling nginx](https://nginx.org/en/docs/control.html) at **nginx.org**.
For more information about advanced signals (for performing live binary upgrades, for example), see [Control nginx](https://nginx.org/en/docs/control.html) at **nginx.org**.
Loading