osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

docs: adoc migration bolding typos; Windows pipe name syntax

This commit is contained in:
Chuck Craft 2022-05-11 19:44:16 -05:00 committed by A Wireshark GitLab Utility
parent 2e5a78dc64
commit 609c0d3881
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/dumpcap.adoc
View File

@ -265,7 +265,7 @@ there are no non-loopback interfaces. If there are no interfaces at all,
Pipe names should be either the name of a FIFO (named pipe) or "-" to Pipe names should be either the name of a FIFO (named pipe) or "-" to
read data from the standard input. On Windows systems, pipe names must be read data from the standard input. On Windows systems, pipe names must be
of the form "\\pipe\.\*pipename*". Data read from pipes must be in of the form +"\\.\pipe\+*pipename*". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host. endianness as the capturing host.

4
doc/tshark.adoc
View File

@ -603,7 +603,7 @@ there are no non-loopback interfaces. If there are no interfaces at all,
Pipe names should be either the name of a FIFO (named pipe) or "-" to Pipe names should be either the name of a FIFO (named pipe) or "-" to
read data from the standard input. On Windows systems, pipe names must be read data from the standard input. On Windows systems, pipe names must be
of the form "\\pipe\.\*pipename*". Data read from pipes must be in of the form +"\\.\pipe\+*pipename*". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host. endianness as the capturing host.
@ -1407,7 +1407,7 @@ This option enables extraction of most important diameter fields from large
capture files. Exactly one text line for each diameter message with matched capture files. Exactly one text line for each diameter message with matched
*diameter.cmd.code* will be printed. *diameter.cmd.code* will be printed.
Empty diameter command code or '*' can be specified to mach any *diameter.cmd.code* Empty diameter command code or +'*'+ can be specified to match any *diameter.cmd.code*
Example: *-z diameter,avp* extract default field set from diameter messages. Example: *-z diameter,avp* extract default field set from diameter messages.

2
doc/wireshark-filter.adoc
View File

@ -124,7 +124,7 @@ You can force case sensitivity using
wsp.header.user_agent matches "(?-i)cldc" wsp.header.user_agent matches "(?-i)cldc"
This is an example of PCRE's *(?*option*)* construct. *(?-i)* performs a This is an example of PCRE's *(?*+option+*)* construct. *(?-i)* performs a
case-sensitive pattern match but other options can be specified as well. More case-sensitive pattern match but other options can be specified as well. More
information can be found in the information can be found in the
pcrepattern(3)|https://www.pcre.org/original/doc/html/pcrepattern.html man page. pcrepattern(3)|https://www.pcre.org/original/doc/html/pcrepattern.html man page.

4
doc/wireshark.adoc
View File

@ -416,7 +416,7 @@ there are no non-loopback interfaces. If there are no interfaces at all,
Pipe names should be either the name of a FIFO (named pipe) or "-" to Pipe names should be either the name of a FIFO (named pipe) or "-" to
read data from the standard input. On Windows systems, pipe names must be read data from the standard input. On Windows systems, pipe names must be
of the form "\\pipe\.\*pipename*". Data read from pipes must be in of the form +"\\.\pipe\+*pipename*". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host. endianness as the capturing host.
@ -548,7 +548,7 @@ Since *Ethereal* 0.10.12, the recent settings replaces the formerly used
-B, -P and -T flags to manipulate the GUI dimensions. -B, -P and -T flags to manipulate the GUI dimensions.
If __prefname__ is "uat", you can override settings in various user access If __prefname__ is "uat", you can override settings in various user access
tables using the form uat*:*__uat filename__:__uat record__. __uat filename__ tables using the form "uat:__uat filename__:__uat record__". __uat filename__
must be the name of a UAT file, e.g. __user_dlts__. __uat_record__ must be in must be the name of a UAT file, e.g. __user_dlts__. __uat_record__ must be in
the form of a valid record for that file, including quotes. For instance, to the form of a valid record for that file, including quotes. For instance, to
specify a user DLT from the command line, you would use specify a user DLT from the command line, you would use