The problem was caused by starting a thread and then forking the program as part of daemonizing it. This resulted in the thread no longer communicating correctly with the forked main program. See here for more information:
http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before- using-them I've created a patch that fixes this problem by creating the daemon fork prior to creating any threads. This has worked OK in my limited testing, but I recommend additional testing before releasing this version on an unsuspecting world. Note also that iperf2 appears to be semi-deprecated in favor of iperf3, which is not yet in Ubuntu. From the iperf2 Sourceforge page: This is the old, Iperf 2 code base. The primary development has moved to Iperf 3 which is hosted on Google Code. You can find it here: http://code.google.com/p/iperf/."; It appears that efforts are underway to bring iperf3 into Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739921 ** Bug watch added: Debian Bug tracker #739921 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739921 ** Patch added: "Patch to fix this bug" https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1260893/+attachment/4144925/+files/nomaxcpu.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260893 Title: iperf forks and loops endlessly in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1260893/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
