diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-31 04:13:00 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-31 04:13:00 +0000 |
commit | dc3f3471f8a00ce0c8fb4cbf2a31e299696f3bbc (patch) | |
tree | e97b4f25c511372d73bdd96c389c5f468d99138a /Documentation/nvme-connect-all.html | |
parent | Adding upstream version 2.2.1. (diff) | |
download | nvme-cli-upstream/2.3.tar.xz nvme-cli-upstream/2.3.zip |
Adding upstream version 2.3.upstream/2.3
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/nvme-connect-all.html')
-rw-r--r-- | Documentation/nvme-connect-all.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/nvme-connect-all.html b/Documentation/nvme-connect-all.html index 46d806b..89eae33 100644 --- a/Documentation/nvme-connect-all.html +++ b/Documentation/nvme-connect-all.html @@ -782,8 +782,8 @@ nvme-connect-all(1) Manual Page <div class="paragraph"><p>Send one or more Discovery requests to a NVMe over Fabrics Discovery
Controller, and create controllers for the returned discovery records.</p></div>
<div class="paragraph"><p>If no parameters are given, then <em>nvme connect-all</em> will attempt to
-find a /etc/nvme/discovery.conf file to use to supply a list of
-connect-all commands to run. If no /etc/nvme/discovery.conf file
+find a /usr/local/etc/nvme/discovery.conf file to use to supply a list of
+connect-all commands to run. If no /usr/local/etc/nvme/discovery.conf file
exists, the command will quit with an error.</p></div>
<div class="paragraph"><p>Otherwise a specific Discovery Controller should be specified using the
--transport, --traddr and if necessary the --trsvcid and a Discovery
@@ -912,7 +912,7 @@ cellspacing="0" cellpadding="4"> <p>
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
+ /usr/local/etc/nvme/hostnqn first. If that does not exist, the
autogenerated NQN value from the NVMe Host kernel module is used next.
The Host NQN uniquely identifies the NVMe Host, and may be used by the
the Discovery Controller to control what NVMe Target resources are
@@ -953,7 +953,7 @@ cellspacing="0" cellpadding="4"> <dd>
<p>
Use the specified JSON configuration file instead of the
- default /etc/nvme/config.json file or <em>none</em> to not read in
+ default /usr/local/etc/nvme/config.json file or <em>none</em> to not read in
an existing configuration file. The JSON configuration file
format is documented in
<a href="https://github.com/linux-nvme/libnvme/doc/config-schema.json">https://github.com/linux-nvme/libnvme/doc/config-schema.json</a>
@@ -1120,7 +1120,7 @@ the RDMA network. Port 4420 is used by default: </li>
<li>
<p>
-Issue a <em>nvme connect-all</em> command using a /etc/nvme/discovery.conf file:
+Issue a <em>nvme connect-all</em> command using a /usr/local/etc/nvme/discovery.conf file:
</p>
<div class="listingblock">
<div class="content">
@@ -1156,7 +1156,7 @@ nvme-connect(1)</p></div> <div id="footer">
<div id="footer-text">
Last updated
- 2022-11-02 16:43:53 CET
+ 2023-01-30 14:14:16 CET
</div>
</div>
</body>
|