Text Processing (Grep/Sed/Awk)

Stop using grep to find files that don’t exist

🧩 The Challenge

Everyone has tried to find a config string by running grep -r across a massive mount, only to get buried in permission denied errors. It’s a total pain to filter out the noise when you just want the data.

💡 The Fix

Instead of fighting grep, use awk to slice through find output so you only touch the files that actually belong to your user. It keeps your terminal clean and saves you from those endless error streams.

find /var/log -user $USER -print 2>/dev/null | xargs awk '/ERROR/ {print FILENAME ": " $0}'

⚙️ Why It Works

Pipe your file list into awk and use the FILENAME variable to keep context while the engine ignores all the directories you don’t have access to anyway. It skips the permissions headache entirely by pre-filtering the input.

🚀 Pro-Tip: Alias this as ‘guser’ so you don’t have to remember the exact syntax when you’re in a hurry.

Linux Tips & Tricks | © ngelinux.com | 9/5/2026