blob: 32082f6b3fb85dac110e9f114dbfc66c002f9550 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
iperf version 2.0.4 running in server mode exits when a client connects
using the -d (duplex) flag.
To reproduce: On machine foo, run server:
[somlo@foo]$ iperf -s
on machine bar, run client in duplex mode:
[somlo@bar]$ iperf -c foo -d
What happens: At the end of the test, the iperf process on machine foo exits.
What *should* happen: At the end of the test, the iperf process on machine
should keep running, listening for new connections.
Patch form L. Gabriel Somlo on the iperf maillist 2009-01-21
---
src/Client.cpp | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Index: src/Client.cpp
===================================================================
--- src/Client.cpp.orig
+++ src/Client.cpp
@@ -207,10 +207,10 @@ void Client::Run( void ) {
char* readAt = mBuf;
#if HAVE_THREAD
- if ( !isUDP( mSettings ) ) {
- RunTCP();
- return;
- }
+// if ( !isUDP( mSettings ) ) {
+// RunTCP();
+// return;
+// }
#endif
// Indicates if the stream is readable
|
