You run locate *.log but get no results, even though you know log files exist. What is the likely problem?

medium📝 Debug Q14 of 15

Linux CLI - Searching and Finding

You run locate *.log but get no results, even though you know log files exist. What is the likely problem?

AThe locate database is corrupted and needs repair

BThe locate command does not support wildcards

CThe shell expands *.log before locate runs, causing no matches

DYou need to run locate with sudo to see log files

Step-by-Step Solution

Solution:

Step 1: Understand shell wildcard expansion
When you run locate *.log, the shell tries to expand *.log to matching files in the current directory before running locate.
Step 2: Effect on locate command
If the current directory contains *.log files, the shell expands to those specific names (e.g., locate error.log access.log), so locate searches only for exact matches to those names system-wide, missing other .log files and causing incomplete or no results. The correct way is to quote the pattern: locate '*.log'.
Final Answer:
The shell expands *.log before locate runs, causing no matches -> Option C
Quick Check:
Quote wildcards to prevent shell expansion [OK]

Quick Trick: Quote wildcards to avoid shell expansion [OK]

Common Mistakes:

Master "Searching and Finding" in Linux CLI

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Linux CLI Quizzes