bug#30719: Progressively compressing piped input

Hi, I have a script which has a logged very repetitive textual output (mostly output of ping and date). To minimize disk usage, I thought to pipe it to gzip -9. Then I realized the log, contrarily to before, remained empty, and recalled the GNU policy of “reading all input and only then outputting

bug#30720: Dead link (translation page) on home page

Hi, Here I found what appears to me to be a dead link (or maybe rather just a broken link): (Translation Project page for Gzip). Except for the proper forementioned web page cleansing/update, out of curiosity,

bug#30719: Progressively compressing piped input

deflate has an inherent latency that accumulates enough data in order to efficiently emit each deflate block. You can deliberately flush (with zlib, not gzip), but if you do that too frequently, e.g. each line, then you will get lousy compression or even expansion. I wrote something called gzlo

bug#30720: Dead link (translation page) on home page

On 03/05/2018 12:49 PM, Garreau, Alexandre wrote: Here I found what appears to me to be a dead link (or maybe rather just a broken link): (Translation Project page for Gzip). That link appears to be an error,