Update the paragraph in 7.12 describing the name of the temp file to include the name used when capturing on multiple interfaces.

svn path=/trunk/; revision=41871

1 files changed, 18 insertions, 14 deletions

diff --git a/help/faq.py b/help/faq.py
index 40f487238f..6e5955d746 100755
--- a/help/faq.py
+++ b/help/faq.py
@@ -1347,21 +1347,25 @@ some platforms (e.g., BSD systems).
 
 <br />
 
-Also, if at all possible, please send a copy of the capture file that
-caused the problem; when capturing packets, Wireshark normally writes
-captured packets to a temporary file, which will probably be in
-<tt>/tmp</tt> or <tt>/var/tmp</tt> on UNIX-flavored OSes, <tt>\TEMP</tt>
-on the main system disk (normally <tt>C:</tt>) on Windows 9x/Me/NT 4.0,
+Also, if at all possible, please send a copy of the capture file that caused
+the problem.  When capturing packets, Wireshark normally writes captured
+packets to a temporary file, which will probably be in <tt>/tmp</tt> or
+<tt>/var/tmp</tt> on UNIX-flavored OSes, <tt>\TEMP</tt> on the main system disk
+(normally <tt>C:</tt>) on Windows 9x/Me/NT 4.0,
 <tt>\Documents and Settings\</tt><var>your login name</var>
-<tt>\Local Settings\Temp</tt> on the main system disk on
-Windows 2000/Windows XP/Windows Server 2003, and
-<tt>\Users\<var>your login name</var>\AppData\Local\Temp</tt> on the main system disk on
-Windows 7, so the capture file will probably be there.  It will have a name
-of the form, <tt>wireshark_iface_YYYYmmddHHMMSS_XXXXXX</tt>.  Please don't
-send a trace file greater than 1 MB when compressed; instead, make it
-available via FTP or HTTP, or say it's available but leave it up to a
-developer to ask for it.  If the trace file contains sensitive
-information (e.g., passwords), then please do not send it.
+<tt>\Local Settings\Temp</tt> on the main system disk on Windows 
+2000/Windows XP/Windows Server 2003, and
+<tt>\Users\<var>your login name</var>\AppData\Local\Temp</tt> on the main
+system disk on Windows 7, so the capture file will probably be there.  If you
+are capturing on a single interface, it will have a name of the form,
+<tt>wireshark_iface_YYYYmmddHHMMSS_XXXXXX</tt>; otherwise, if you are capturing
+on multiple interfaces, it will have a name of the form,
+<tt>wireshark_&lt;N&gt;_interfaces_YYYYmmddHHMMSS_XXXXXX</tt>, where &lt;N&gt;
+is the number of simultaneous interfaces you are capturing on.  Please don't
+send a trace file greater than 1 MB when compressed; instead, make it available
+via FTP or HTTP, or say it's available but leave it up to a developer to ask
+for it.  If the trace file contains sensitive information (e.g., passwords),
+then please do not send it.
 """)