The --server-socket-path and --client-socket-path options
have already been removed. So also remove them from the doc
to avoid confusion.
Fixes: 09f4aa2b955f ("app/pdump: remove unused socket path options")
Cc: sta...@dpdk.org
Signed-off-by: Tiwei Bie <tiwei....@intel.com>
---
doc/guides/tools/pdump.rst | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/doc/guides/tools/pdump.rst b/doc/guides/tools/pdump.rst
index 5168c81ab..7c2b73e72 100644
--- a/doc/guides/tools/pdump.rst
+++ b/doc/guides/tools/pdump.rst
@@ -42,8 +42,6 @@ The tool has a number of command line options:
[ring-size=<ring size>],
[mbuf-size=<mbuf data size>],
[total-num-mbufs=<number of mbufs>]'
- [--server-socket-path=<server socket dir>]
- [--client-socket-path=<client socket dir>]
The ``--pdump`` command line option is mandatory and it takes various sub
arguments which are described in
below section.
@@ -56,14 +54,6 @@ below section.
* Multiple instances of ``--pdump`` can be passed to capture packets on
different port and queue combinations.
-The ``--server-socket-path`` command line option is optional. This represents
the server socket directory.
-If no value is passed default values are used i.e. ``/var/run/.dpdk/`` for
root users and ``~/.dpdk/``
-for non root users.
-
-The ``--client-socket-path`` command line option is optional. This represents
the client socket directory.
-If no value is passed default values are used i.e. ``/var/run/.dpdk/`` for
root users and ``~/.dpdk/``
-for non root users.
-
The ``--pdump`` parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.14.5
