From owner-freebsd-ports@FreeBSD.ORG  Tue Apr  6 09:57:43 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EE69416A4CE
	for <freebsd-ports@freebsd.org>; Tue,  6 Apr 2004 09:57:43 -0700 (PDT)
Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E06BD43D55
	for <freebsd-ports@freebsd.org>; Tue,  6 Apr 2004 09:57:43 -0700 (PDT)
	(envelope-from mhunter@ack.Berkeley.EDU)
Received: (from mhunter@localhost)
	by ack.Berkeley.EDU (8.11.3/8.11.3) id i36GuWb20813
	for freebsd-ports@freebsd.org; Tue, 6 Apr 2004 09:56:32 -0700 (PDT)
Date: Tue, 6 Apr 2004 09:56:32 -0700
From: Mike Hunter <mhunter@ack.Berkeley.EDU>
To: freebsd-ports@freebsd.org
Message-ID: <20040406165632.GA20719@ack.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: Iperf doesn't hang up with clients, breaks perl's STDIN...?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2004 16:57:44 -0000

Easily reproducible for me is that an iperf server launched via "iperf -s -D"
never seems to hangup with remote clients...the 10 seconds pass and the
client just sits there.

There's an interesting related problem I'm having with iperf and perl.
I have a perl fragment that looks like this:

my $input = <STDIN>;
if ($input =~ /yes/i)
{
	system("iperf -s -D >/dev/null");
}
$input = <STDIN>;
die "wtf!!!" unless defined $input;

It dies with "wtf!!!".  Somehow running iperf is breaking my perl script's
connection to its own STDIN.

Not sure if you read, but in the move to 5 the number of /dev/fd's was
reduced from 64 to 3...I have a theory that iperf is trying to do
something weird with its file descriptors and that's what's causing the
problem.

I'd appreciate any help you can give or any suggestions where else to ask
around.

As an aside, do you know the status of the iperf project?  Their web
paged looked a bit long in the tooth to me.

Thanks for your help,

Mike