RE: DAST: Iperf - Newbie Question - najaf --at-- uab.edu
Iperf is only memory to memory (no file transfer capabilities). Fot file transfer applications see bbftp (http://doc.in2p3.fr/bbftp/), bbcp (http://www.slac.stanford.edu/~abh/bbcp/) or GridFTP (http://www-fp.globus.org/datagrid/gridftp.html). All three of these have similar capabilities to iperf (settable windows, multi streams, etc.)
-----Original Message-----
From: owner-iperf-users --at-- dast.nlanr.net [mailto:owner-iperf-users --at-- dast.nlanr.net] On Behalf Of Mitch Kutzko
Sent: Thursday, July 07, 2005 5:46 AM
To: Iperf Users
Subject: DAST: Iperf - Newbie Question - najaf --at-- uab.edu
>Date: Wed, 6 Jul 2005 23:56:08 -0500
>To: najaf --at-- uab.edu
>Subject: DAST: Iperf - Newbie Question - najaf --at-- uab.edu
>
>
>Contacting DAST re: Request for information about Iperf
>From: Najaf Shah <najaf --at-- uab.edu>
>
>Subject: Newbie Question
>
>Question/Comment:
>Hi,
> I've just begun using Iperf and have a question about it. When
>sending files from a client to a server, is it possible to recover the
>actual file at the server's end? For example, if I'm sending a text
>file from the client to the server, is there an Iperf command that'll
>let me save the file the server receives in a certain location?
>
>In all other respects, Iperf is almost perfect for the experiments I
>have to run for my project. But I really do need to be able to look at
>the file (or whatever part was transferred) at the receiving end.
>
>Can Iperf or some other tool in combination with Iperf accomplish this
>easily? Any advice will be appreciated.
>
>Thank you
>
>
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199 http://hobbes.ncsa.uiuc.edu/