qinhan620 / iperf

Automatically exported from code.google.com/p/iperf
0 stars 0 forks source link

Save data to log file #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
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.

Original issue reported on code.google.com by richih.m...@gmail.com on 6 Aug 2010 at 8:49

GoogleCodeExporter commented 8 years ago
Hmm, is there some reason this is preferred over just using shell redirection?

Original comment by jdugan.e...@gmail.com on 6 Aug 2010 at 9:37

GoogleCodeExporter commented 8 years ago
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.

Original comment by kennethw...@gmail.com on 11 Aug 2010 at 9:37

GoogleCodeExporter commented 8 years ago
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.

Original comment by viet...@hotmail.com on 26 Oct 2010 at 11:07

GoogleCodeExporter commented 8 years ago

Original comment by bltier...@gmail.com on 7 Sep 2012 at 3:55

GoogleCodeExporter commented 8 years ago

Original comment by jdu...@es.net on 10 Sep 2012 at 4:24

GoogleCodeExporter commented 8 years ago
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.

Original comment by jef.posk...@gmail.com on 13 Dec 2012 at 2:37

GoogleCodeExporter commented 8 years ago
Thanks for the update.

Wouldn't it make sense to re-open this issue and state that it will use 
-o-/--output, instead? That way, it can be tracked easily.

Alternatively, I can open a new issue for support for it, if you prefer.

Original comment by richih.m...@gmail.com on 13 Dec 2012 at 4:10

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
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.

Original comment by aaron.hamid on 15 Nov 2013 at 12:45

GoogleCodeExporter commented 8 years ago
Hi all,
have you solved the problem of --output? how?
I have to save my results...

Original comment by fichera....@gmail.com on 23 Dec 2013 at 8:59