показать таблицу имен TIPC (show TIPC nametable)
Имя (Name)
tipc-nametable - show TIPC nametable
Синопсис (Synopsis)
tipc nametable show
Параметры (Options)
Options (flags) that can be passed anywhere in the command chain.
-h, --help
-j, -json
Output results in JavaScript Object Notation (JSON).
-p, -pretty
The default JSON format is compact and more efficient to
parse but hard for most users to read. This flag adds
indentation for readability.
Show help about last valid command. For example tipc
nametable --help will show nametable help and tipc --help
will show general help. The position of the option in the
string is irrelevant.
Описание (Description)
The nametable shows TIPC publication information.
Nametable format
Type
The 32-bit type field of the port name. The type field
often indicates the class of service provided by a port.
Lower
The lower bound of the 32-bit instance field of the port
name. The instance field is often used as as a sub-class
indicator.
Upper
The upper bound of the 32-bit instance field of the port
name. The instance field is often used as as a sub-class
indicator. A difference in lower and upper means the
socket is bound to the port name range [lower,upper]
Port Identity
The unique socket (port) identifier within the TIPC
cluster. The port identity consists of a node identity
followed by a socket reference number.
Publication
The publication ID is a random number used internally to
represent a publication.
Scope
The publication scope specifies the visibility of a bound
port name. The scope can be specified to comprise three
different domains: node, cluster and zone. Applications
residing within the specified scope can see and access the
port using the displayed port name.
Статус выхода (Exit)
Exit status is 0 if command was successful or a positive integer
upon failure.
Смотри также (See also)
tipc(8), tipc-bearer(8), tipc-link(8), tipc-media(8),
tipc-node(8), tipc-peer(8), tipc-socket(8)
Сообщение об ошибках (Reporting bugs)
Report any bugs to the Network Developers mailing list
<netdev@vger.kernel.org> where the development and maintenance is
primarily done. You do not have to be subscribed to the list to
send a message there.
