Re: iperf and Deamon mode...


Well the non-windows version of Iperf closes stdin and stdout after it 
displays the process ID. It will then open a iperf log file for writing 
results and such. Check your log directory for it.

Kevin

On Sat, 7 Jun 2003, Mitch Kutzko wrote:

> >Date: Sat, 07 Jun 2003 12:55:59 -0700
> >From: Phil Reese <preese --at-- stanford.edu>
> >To: iperf-users --at-- dast.nlanr.net
> >Subject: iperf and Deamon mode...
> >
> >I'm putting together a system for network monitoring on campus.  It will be a
> >simple Linux box with a gig copper nic.  I'll be running the Network
> Diagnostic
> >Tool (NDT) from Argonne National Laboratory and I'd like to have 'iperf'
> running
> >all the time too.
> >
> >When I use the 'iperf -s -D > logfile' option on Linux, all I get in the
> >'logfile' is the following:
> >[root --at-- linux ip]# more iplog
> >------------------------------------------------------------
> >Server listening on TCP port 5001
> >TCP window size: 85.3 KByte (default)
> >------------------------------------------------------------
> >Running Iperf Server as a daemon
> >The Iperf daemon process ID : 11644
> >
> >I've then run a number of clients against this server and the logfile doesn't
> >change.
> >
> >When I run iperf as a server and daemon on windows, the logfile generated has
> >more interesting stuff:
> >------------------------------------------------------------
> >Server listening on TCP port 5001
> >TCP window size: 8.00 KByte (default)
> >------------------------------------------------------------
> >[160] local 192.168.1.3 port 5001 connected with 192.168.1.100 port 32771
> >[ ID] Interval       Transfer     Bandwidth
> >[160]  0.0-10.0 sec   109 MBytes  91.3 Mbits/sec
> >
> >
> >I'm clearly doing something wrong but I can't figure it out!  If this
> happens to
> >be a bug in the Linux version of 1.7.0, could I put a pitch in for a simple
> >'date' command addition to the output?  The logs would be more helpful to
> me if
> >I knew when the tests were being done in addition to the IP address and the
> >results.
> >
> >Phil Reese
> >Stanford University
> >Network Systems, CNS
> >Information Technology Systems and Services
> >Pine Hall, Room 126
> >(650) 723-4328
> >preese --at-- stanford.edu
> 
> --
> Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
> http://hobbes.ncsa.uiuc.edu/
> 



Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index