From 02541c220e2889e4315d6044cdb1f6690a245668 Mon Sep 17 00:00:00 2001 From: Lucas Trzesniewski Date: Mon, 16 Jan 2023 19:36:35 +0100 Subject: [PATCH] Fix environment variable name --- documentation/design-docs/ipc-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/design-docs/ipc-protocol.md b/documentation/design-docs/ipc-protocol.md index 42c28f7b30..24fb0e5ec3 100644 --- a/documentation/design-docs/ipc-protocol.md +++ b/documentation/design-docs/ipc-protocol.md @@ -950,7 +950,7 @@ Example usage: $ export DOTNET_DiagnosticPorts=$DOTNET_DiagnosticPorts;~/mydiagport.sock,nosuspend; ``` -Any diagnostic ports specified in this configuration will be created in addition to the default port (`dotnet-diagnostic--`). The suspend mode of the default port is set via the new environment variable `DOTNET_DefaultDotnetPortSuspend` which defaults to `0` for `nosuspend`. +Any diagnostic ports specified in this configuration will be created in addition to the default port (`dotnet-diagnostic--`). The suspend mode of the default port is set via the new environment variable `DOTNET_DefaultDiagnosticPortSuspend` which defaults to `0` for `nosuspend`. Each port configuration specifies whether it is a `suspend` or `nosuspend` port. Ports specifying `suspend` in their configuration will cause the runtime to pause early on in the startup path before most runtime subsystems have started. This allows any agent to receive a connection and properly setup before the application startup continues. Since multiple ports can individually request suspension, the `resume` command needs to be sent by each suspended port connection before the runtime resumes execution.