From 06c3372b145280dead5ec436e0a03a46213f17f1 Mon Sep 17 00:00:00 2001 From: "Mark D. Roth" Date: Mon, 14 Oct 2024 15:32:44 +0000 Subject: [PATCH] [doc] clarify absolute path format for unix URIs --- doc/naming.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/naming.md b/doc/naming.md index 8d385915b19..e6d3bd09b72 100644 --- a/doc/naming.md +++ b/doc/naming.md @@ -34,12 +34,12 @@ Most gRPC implementations support the following URI schemes: resolver does not support this, but the c-ares based resolver supports specifying this in the form "IP:port".) -- `unix:path`, `unix://absolute_path` -- Unix domain sockets (Unix systems only) +- `unix:path`, `unix:///absolute_path` -- Unix domain sockets (Unix systems only) - `path` indicates the location of the desired socket. - In the first form, the path may be relative or absolute; in the - second form, the path must be absolute (i.e., there will actually be - three slashes, two prior to the path and another to begin the - absolute path). + second form, the path must be absolute (i.e., the last of the three + slashes is actually part of the path, so the path part of the URI is + `/absolute_path`). - `unix-abstract:abstract_path` -- Unix domain socket in abstract namespace (Unix systems only) - `abstract_path` indicates a name in the abstract namespace.