| | 1 | Summary: Counting pipe |
| | 2 | Summary(pl): Potok ze zliczaniem |
| | 3 | Name: cpipe |
| | 4 | Version: 3.0.1 |
| | 5 | Release: 2 |
| | 6 | License: GPL |
| | 7 | Group: Applications/Archiving |
| | 8 | Source0: http://download.berlios.de/cpipe/%{name}-%{version}.tar.gz |
| | 9 | # Source0-md5: 1eaa5b28ef7ef96f1c54d5607ec828b3 |
| | 10 | Patch0: %{name}-make_fix.patch |
| | 11 | URL: http://developer.berlios.de/projects/cpipe/ |
| | 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 |
| | 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? |
| | 19 | |
| | 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. |
| | 26 | |
| | 27 | %description -l pl |
| | 28 |
projects / packages / cpipe.git / blame_incremental