Issue 24 in iperf: Save data to log file

[ip...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement

New issue 24 by richih.mailinglist: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

Explaination of new feature

-L or --log-file will save all data to a log file.
iperf will quit with an error if the target file exists unless -A or
--append is specified.
Both a client & server option.

Justification of new feature

I need to keep logs, sometimes.

[ip...@googlecode.com]

Comment #1 on issue 24 by jdugan.esnet: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

Hmm, is there some reason this is preferred over just using shell
redirection?

[ip...@googlecode.com]

Comment #2 on issue 24 by kennethw...@gmail.com: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

I would prefer to be able to output a complete test as one txt file. They
can collect in a directory. Then get sucked into a db for later use.

[ip...@googlecode.com]

Comment #3 on issue 24 by viet...@hotmail.com: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

I thought it was the --output command argument that would save the data to
a specified file, but it doesnt work or I could be doing something wrong.

-c <IPaddress> --output data.txt
Somehow I could not find that data.txt file.

[ip...@googlecode.com]

Updates:
Labels: -Milestone-3.0-Release Milestone-3.0b1
Blockedon: iperf:15

Comment #5 on issue 24 by jdu...@lbl.gov: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

(No comment was entered for this change.)

[ip...@googlecode.com]

Updates:
Status: WontFix

Comment #6 on issue 24 by jef.posk...@gmail.com: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

Looks like -o/--output existed in a previous version but in not in the
current version. The consensus in yesterday's meeting was that if --output
existed then we should fix it, otherwise people should just use shell
redirection and we'll mark this WontFix. So, WontFix.

[ip...@googlecode.com]

Comment #8 on issue 24 by fujisk...@gmail.com: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

The problem with shell redirection is that output apparently isn't
generated if the shell is not interactive. I'm running iperf from scripts
executed by a crontab, and I have iperf's output redirected to log files in
these scripts. But there's no output. Every file generated is zero
bytes. If I run these same scripts from a shell command-line, iperf's
logging is redirected and saved normally, and these files are greater than
zero bytes.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ip...@googlecode.com]

Comment #9 on issue 24 by aaron.hamid: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

yes, -o/--output should be fixed. it's very misleading. in the version I
have used, 2.0.5, the flag is documented in help, but does nothing (and
gives no error). this is very confusing and I wasted some time trying
variations. in windows io redirection seems shaky and all results don't
seem to be flushed to the file after hard-cancelling the process.

[ip...@googlecode.com]

Comment #10 on issue 24 by fichera....@gmail.com: Save data to log file
http://code.google.com/p/iperf/issues/detail?id=24

Hi all,
have you solved the problem of --output? how?
I have to save my results...

[ip...@googlecode.com]

Comment #11 on issue 24 by gu...@gaikai.com: Save data to log file
https://code.google.com/p/iperf/issues/detail?id=24

I can confirm it is still buggy in 2.0.5-r2

[ip...@googlecode.com]

Comment #12 on issue 24 by gu...@gaikai.com: Save data to log file
https://code.google.com/p/iperf/issues/detail?id=24

and redirection does not work in daemon mode... I better look at the code
at this point