Adding upstream version 2.3.upstream/2.3

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 6 insertions, 6 deletions

diff --git a/Documentation/nvme-discover.1 b/Documentation/nvme-discover.1
index 547900c..cc5dc49 100644
--- a/Documentation/nvme-discover.1
+++ b/Documentation/nvme-discover.1
@@ -2,12 +2,12 @@
 .\"     Title: nvme-discover
 .\"    Author: [see the "AUTHORS" section]
 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\"      Date: 11/02/2022
+.\"      Date: 01/30/2023
 .\"    Manual: NVMe Manual
 .\"    Source: NVMe
 .\"  Language: English
 .\"
-.TH "NVME\-DISCOVER" "1" "11/02/2022" "NVMe" "NVMe Manual"
+.TH "NVME\-DISCOVER" "1" "01/30/2023" "NVMe" "NVMe Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -63,7 +63,7 @@ nvme-discover \- Send Get Log Page request to Discovery Controller\&.
 .sp
 Send one or more Get Log Page requests to a NVMe\-over\-Fabrics Discovery Controller\&.
 .sp
-If no parameters are given, then \fInvme discover\fR will attempt to find a /etc/nvme/discovery\&.conf file to use to supply a list of Discovery commands to run\&. If no /etc/nvme/discovery\&.conf file exists, the command will quit with an error\&.
+If no parameters are given, then \fInvme discover\fR will attempt to find a /usr/local/etc/nvme/discovery\&.conf file to use to supply a list of Discovery commands to run\&. If no /usr/local/etc/nvme/discovery\&.conf file exists, the command will quit with an error\&.
 .sp
 Otherwise, a specific Discovery Controller should be specified using the \-\-transport, \-\-traddr, and if necessary the \-\-trsvcid flags\&. A Discovery request will then be sent to the specified Discovery Controller\&.
 .SH "BACKGROUND"
@@ -142,7 +142,7 @@ This field specifies the network interface used on the host to connect to the Co
 .PP
 \-q <hostnqn>, \-\-hostnqn=<hostnqn>
 .RS 4
-Overrides the default host NQN that identifies the NVMe Host\&. If this option is not specified, the default is read from /etc/nvme/hostnqn first\&. If that does not exist, the autogenerated NQN value from the NVMe Host kernel module is used next\&.
+Overrides the default host NQN that identifies the NVMe Host\&. If this option is not specified, the default is read from /usr/local/etc/nvme/hostnqn first\&. If that does not exist, the autogenerated NQN value from the NVMe Host kernel module is used next\&.
 .RE
 .PP
 \-I <hostid>, \-\-hostid=<hostid>
@@ -166,7 +166,7 @@ This field takes a device as input\&. Device is in the format of nvme*, eg\&. nv
 .PP
 \-C <cfg>, \-\-config\-file=<cfg>
 .RS 4
-Use the specified JSON configuration file instead of the default /etc/nvme/config\&.json file or
+Use the specified JSON configuration file instead of the default /usr/local/etc/nvme/config\&.json file or
 \fInone\fR
 to not read in an existing configuration file\&. The JSON configuration file format is documented in
 \m[blue]\fBhttps://github\&.com/linux\-nvme/libnvme/doc/config\-schema\&.json\fR\m[]
@@ -278,7 +278,7 @@ Query the Discover Controller with IP4 address 192\&.168\&.1\&.3 for all resourc
 .\}
 Issue a
 \fInvme discover\fR
-command using a /etc/nvme/discovery\&.conf file:
+command using a /usr/local/etc/nvme/discovery\&.conf file:
 .sp
 .if n \{\
 .RS 4