projects / packages / cpipe.git / blame
| Commit | Line | Data |
|---|---|---|
| f96a0b6f | 1 | Summary: Counting pipe |
| 2 | Summary(pl): Potok ze zliczaniem | |
| 26fbce0d | 3 | Name: cpipe |
| 23196b69 | 4 | Version: 3.0.1 |
| 5c65ff5f | 5 | Release: 2 |
| 26fbce0d SZ |
6 | License: GPL |
| 7 | Group: Applications/Archiving | |
| edba68b2 | 8 | Source0: http://download.berlios.de/cpipe/%{name}-%{version}.tar.gz |
| 23196b69 | 9 | # Source0-md5: 1eaa5b28ef7ef96f1c54d5607ec828b3 |
| 3787f14f | 10 | Patch0: %{name}-make_fix.patch |
| 45397fe8 | 11 | URL: http://developer.berlios.de/projects/cpipe/ |
| 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 |