osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

FAQ: Fix some markup

This commit is contained in:
Gerald Combs 2023-01-08 17:52:00 -08:00
parent 56deed1c15
commit 4d38cf9ec6
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docbook/faq.adoc
View File

@ -632,9 +632,8 @@ Also, if at all possible, please send a copy of the capture file that
caused the problem. When capturing packets, Wireshark normally writes caused the problem. When capturing packets, Wireshark normally writes
captured packets to a temporary file, which will probably be in `/tmp` captured packets to a temporary file, which will probably be in `/tmp`
or `/var/tmp` on UNIX-flavored OSes, `\TEMP` on the main system disk or `/var/tmp` on UNIX-flavored OSes, `\TEMP` on the main system disk
(normally `\Documents and Settings\`your login name (normally `\Documents and Settings\<your login name>\Local Settings\Temp` on the main system disk on Windows XP and
`\Local Settings\Temp` on the main system disk on Windows XP and Server 2003, and `\Users\<your login name>\AppData\Local\Temp` on the main
Server 2003, and `\Users\your login name\AppData\Local\Temp` on the main
system disk on Windows Vista and later, so the capture file will system disk on Windows Vista and later, so the capture file will
probably be there. If you are capturing on a single interface, it will probably be there. If you are capturing on a single interface, it will
have a name of the form, have a name of the form,