projects / packages / cpipe.git / blame
| Commit | Line | Data |
|---|---|---|
| 26fbce0d SZ |
1 | Summary: counting pipe |
| 2 | Summary(pl): potok ze zliczaniem | |
| 3 | Name: cpipe | |
| 4 | Version: 2.0.0 | |
| 5 | Release: 1 | |
| 6 | License: GPL | |
| 7 | Group: Applications/Archiving | |
| 8 | Group(de): Applikationen/Archivierung | |
| 9 | Group(pl): Aplikacje/Archiwizacja | |
| 10 | Source0: http://wsd.iitb.fhg.de/~kir/cpipehome/%{name}-%{version}.tar.gz | |
| a6f2c5d7 | 11 | URL: http://wsd.iitb.fhg.de/~kir/cpipehome/ |
| 26fbce0d SZ |
12 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) |
| 13 | ||
| 14 | %description | |
| 15 | Did you ever want to know how fast your tar is or how much data it has | |
| da4b2007 | 16 | transferred already. How about using socket or nc to copy files either |
| 17 | with or without compression over a fast network connection, which one | |
| 18 | is faster? | |
| 26fbce0d | 19 | |
| da4b2007 | 20 | If you want to know the answer, use cpipe as a totally unscientific |
| 21 | approach to measure throughput. Cpipe copies its standard input to its | |
| 22 | standard output while measuring the time it takes to read an input | |
| 23 | buffer and write an output buffer. Statistics of average throughput | |
| 24 | and the total amount of bytes copied are printed to the standard error | |
| 25 | output. | |
| 26fbce0d SZ |
26 | |
| 27 | %description -l pl | |
| da4b2007 | 28 |