How to Use the `find` Command in Linux Like a Pro

Use -name for case-sensitive and -iname for case-insensitive file searches. 2. Filter by type with -type (f, d, l), by size with -size ( 100M, -50K), and by modification time with -mtime (-7, 30) or -mmin. 3. Execute actions on found files using -exec with {} \; or {} for efficiency, and test with echo first. 4. Combine conditions using AND (implied), OR (-o), NOT (! or -not), and parentheses \( \) for grouping. 5. Optimize by avoiding permission errors (2>/dev/null), limiting depth with -maxdepth, and starting searches in specific directories. Real-world examples include compressing old logs, finding large directories, deleting empty files, and detecting SUID files for security, all demonstrating how mastering find enhances efficiency and control in Linux environments.

The find command in Linux is one of the most powerful tools for searching and managing files directly from the terminal. While basic usage is simple, mastering find unlocks advanced file operations that save time and boost productivity. Here’s how to use find like a pro — going beyond basic searches to real-world, efficient workflows.

1. Search Files by Name (Case-Sensitive and Case-Insensitive)

The most common use of find is locating files by name.

find /path/to/search -name "filename.txt"

This searches for files named exactly filename.txt. The search is case-sensitive.

For a case-insensitive search, use -iname:

find /home -iname "*.txt"

This finds all .txt files under /home, regardless of whether they’re .TXT, .Txt, etc.

? Tip: Always quote patterns with wildcards (*, ?) to prevent the shell from expanding them prematurely.

2. Filter by File Type, Size, and Modification Time

Pro users combine filters to narrow results precisely.

By File Type

Use -type to specify what kind of file you're looking for:

• f = regular file
• d = directory
• l = symbolic link

find /var/log -type f -name "*.log"

Finds only regular files ending in .log.

By Size

Search files based on size using -size:

• 100M → larger than 100 megabytes
• -50K → smaller than 50 kilobytes
• 1G → exactly 1 gigabyte (rarely used)

find ~ -type f -size  1G

Finds all files in your home directory bigger than 1GB.

By Modification Time

Use -mtime to find files modified n days ago:

• -mtime -7 → changed in the last 7 days
• -mtime 30 → unchanged for more than 30 days

find /var/log -type f -name "*.log" -mtime  30

Finds log files older than 30 days — useful for cleanup.

You can also use -mmin for minutes (great for monitoring recent changes):

find . -type f -mmin -5

Finds files modified in the last 5 minutes in the current directory.

3. Execute Commands on Found Files with -exec

One of find's superpowers is running actions on matched files using -exec.

Delete Files Safely

Instead of risky rm *.log (which can fail with too many files), use:

find /tmp -name "*.tmp" -type f -exec rm -f {} \;

• {} is a placeholder for each found file.
• \; ends the command (runs once per file).

For better performance with many files, use instead of \;:

find /tmp -name "*.tmp" -type f -exec rm -f {}  

This passes multiple files to a single rm call — faster and safer.

Change Permissions or Ownership

Fix permissions on config files:

find /home -name "*.conf" -type f -exec chmod 644 {} \;

Or change ownership:

find /opt/apps -type d -name "logs" -exec chown admin:admin {} \;

Preview Before Running

Always test first! Replace the action with echo:

find . -name "*.bak" -exec echo "Would delete: {}" \;

This shows what would be affected before making changes.

4. Combine Conditions with AND, OR, NOT

find supports logical operators to build complex queries.

• AND is implied when chaining expressions:

  find /tmp -type f -name "*.tmp" -mtime  7

  Means: regular file AND name ends in .tmp AND modified over 7 days ago.

• OR uses -o:

  find . -name "*.txt" -o -name "*.log"

  Finds .txt OR .log files.

• NOT uses -not or ! (escape ! in some shells):

  find . -type f ! -name "*.pdf"

  All files that are not PDFs.

? Use parentheses to group conditions. Escape them with \ or quote:

find . \( -name "*.txt" -o -name "*.md" \) -mtime -7

Finds .txt or .md files modified in the last 7 days.

5. Optimize and Avoid Common Pitfalls

Even pros make mistakes. Here’s how to stay sharp:

• Avoid permission noise: Redirect errors when searching system dirs:

  find / -name "secret.conf" 2>/dev/null

  Suppresses "Permission denied" spam.

• Start specific: Don’t search from / unless necessary. Narrow the path:

  find ~/Documents -name "*.odt"

• Use -maxdepth to limit recursion:

  find /etc -maxdepth 2 -name "*.conf"

  Only searches /etc and immediate subdirectories.

• Don’t parse ls output: find outputs clean paths — perfect for scripting.

Bonus: Real-World Pro Examples

Here are some practical one-liners you’ll actually use:

• Find and compress old logs:

  find /var/log -name "*.log" -mtime  30 -exec gzip {} \;

• Locate large directories:

  find /home -type d -exec du -sh {} \; | sort -hr | head -10

• Find empty files and delete them:

  find . -type f -empty -delete

• Find files with SUID bit set (security check):

  find / -type f -perm /4000 2>/dev/null

  ---

  Mastering find isn’t about memorizing every option — it’s about understanding how to chain conditions and actions to solve real problems efficiently. Once you’re comfortable combining name, type, time, size, and -exec, you’ll wonder how you ever managed without it.

  Basically, start small, test often, and build up. The command looks cryptic at first, but soon becomes second nature.

  The above is the detailed content of How to Use the `find` Command in Linux Like a Pro. For more information, please follow other related articles on the PHP Chinese website!