Re: iperf and Deamon mode...
Yes it closes both the stdout and stderr filehandles and opens a log
connection. Judging from my recent tinkering with this feature, I would
think that it does not work. I have never used it nor ever heard of
someone doing it either. I have never messed with this code nor understand
it. It opens a connection to the syslog logger but still uses printf not
syslog() to print messages so it looks pretty worthless. =-( If you
download the source in src/Listener.cpp is a function called runAsDaemon
if you comment out the last 3 lines 2 fclose's and one openlog then the
behavior you want will occur.
Kevin
On Mon, 9 Jun 2003, Phil Reese wrote:
> Kevin,
>
> Here is a step by step of what I've done:
>
> [root --at-- linux tt]# tar -zxvf iperf-1.7.0-linux-2.1.tar.gz
> iperf
> doc/
> doc/CVS/
> doc/CVS/Root
> doc/CVS/Repository
> doc/CVS/Entries
> doc/dast.gif
> doc/jperf.gif
> doc/lib.html
> doc/ui_license.html
> doc/index.html
> README
> KNOWN_PROBLEMS
> [root --at-- linux tt]# ./iperf -s -D > iperflog
> **** Went to another machine and ran a few successful iperf tests against this
> system. ****
> [root --at-- linux tt]# more iperflog
> ------------------------------------------------------------
> Server listening on TCP port 5001
> TCP window size: 85.3 KByte (default)
> ------------------------------------------------------------
> Running Iperf Server as a daemon
> The Iperf daemon process ID : 4535
> [root --at-- linux tt]#
>
> You say to 'Check your log directory for it.', I expected to check the file I
> redirected output to, iperflog, are you suggesting the results go somewhere else?
> I've looked in /var/log.
>
> Thanks for your time looking at this,
> Phil
>
>
> Kevin Gibbs wrote:
>
> > 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
> >
>