There I said it !
How do you propose zcat tell the difference between an uncompressed file and a corrupted compressed file? Or are you saying if it doesn't recognize it as compressed, just dump the source file regardless? Because that could be annoying.
Yeah, it's a pain. Leads to bad one liners:
for i in $(ls); do zcat $i || cat $i; doneThat's really bad.
zcat ./* 2>/dev/null || cat ./*does the same.Btw, don't parse ls. Use
find |while read -rinstead.Won't this cause cat to iterate through all files in the cwd once zcat encounters an issue, instead of just the specific file?
Thanks !
But still we shouldn't have to resort to this !
Also, can't get the output through pipefor i in $(ls); do zcat $i || cat $i; done | grep mysearchtermthis appears to workfind . -type f -print0 | xargs -0 -I{} sh -c 'zcat "{}" 2>/dev/null || cat "{}"' | grep "mysearchterm"Still, that was a speed bump that I guess everyone dealing with mass compressed log files has to figure out on the fly because zcat can't read uncompressed files ! argg !!!for i in $(ls); do zcat $i 2>/dev/null || cat $i; done | grep mysearchterm
