I agree. zgrep also works for uncompressed files, so we could use e.g. zgrep ^ instead of zcat.
this post was submitted on 18 Dec 2024
32 points (88.1% liked)
Linux
48622 readers
1394 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Thanks, didn't know that existed
That's basically everything I was looking for !
Yeah, it's a pain. Leads to bad one liners:
for i in $(ls); do zcat $i || cat $i; done
That's really bad. zcat ./* 2>/dev/null || cat ./* does the same.
Btw, don't parse ls. Use find |while read -r instead.
Thanks !
But still we shouldn't have to resort to this !
~~Also, can't get the output through pipe~~
for i in $(ls); do zcat $i || cat $i; done | grep mysearchterm
~~this appears to work~~
~~find . -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
Celeste. Are you here? In a future search maybe?