Set the pipe read timeout to 100 milliseconds instead of 100 microseconds.
authorgerald <gerald@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 17 Nov 2010 23:51:31 +0000 (23:51 +0000)
committergerald <gerald@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 17 Nov 2010 23:51:31 +0000 (23:51 +0000)
Should fix bug 5309.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@34938 f5534014-38df-0310-8fa8-9805f1628bb7

dumpcap.c

index f323f43ccca60db5eaa4fc6e02173b14a1e7bddb..818551dc596b644303ad2993192b8a222092dbea 100644 (file)
--- a/dumpcap.c
+++ b/dumpcap.c
@@ -299,13 +299,11 @@ static gboolean need_timeout_workaround;
  * in OS X 10.6, 10.6.1, 10.6.3, and 10.6.4, so we always use a timeout
  * of 250ms, i.e. the same value as CAP_READ_TIMEOUT when not on one
  * of the offending versions of Snow Leopard.
- *
- * XXX - why is it 100 for threaded capturing?
  */
 #ifndef USE_THREADS
 #define PIPE_READ_TIMEOUT   250000
 #else
-#define PIPE_READ_TIMEOUT   100
+#define PIPE_READ_TIMEOUT   100000
 #endif
 static const char *cap_pipe_err_str;