grep is the core tool used in Linux for text search, which can quickly find content through pattern matching; its basic syntax is grep [options] PATTERN [FILE...], for example, grep "error" /var/log/syslog can find lines containing "error". It is case-sensitive by default. Use the -i option to ignore case, such as grep -i "error" /var/log/syslog; supports regular expressions, 1. Use ^ to match the beginning of the line, such as grep "^Failed" /var/log/auth.log; 2. Use $ to match the end of the line, such as grep "ssh$" /var/log/auth.log; 3. Use . Match any character, indicating that the previous character appears zero or multiple times, such as grep "err." file.txt; 4. Use -E to enable extended regular expressions, combined with ? to represent optional characters, such as grep -E "colou?r" file.txt to match "color" and "colour"; common options include: 1. -r or -R for recursive search, such as grep -r "function myFunction" /home/user/projects; 2. -l only displays file names containing matches, such as grep -rl "TODO" /code/; 3. -n displays line numbers of matching rows, such as grep -n "password" config.php; 4. -v reverse match, displays mismatched rows, such as grep -v "^#" /etc/nginx/nginx.conf Comment lines can be filtered; 5. -A, -B, and -C display the number of lines after, before and in context respectively, such as grep -A 3 -B 2 "error" log.txt can output 3 and 2 lines before and after the matching lines; it can be used in combination with other commands: 1. Filter ps output through the pipeline, such as ps aux | grep nginx; 2. Use -c to count the number of lines, such as grep -c "warning" system.log; 3. Chain filtering, such as grep "fatal" system.log | grep -v "ignored" can exclude specific content; 4. Use -E and | to achieve multi-pattern matching, such as grep -E "error|fail|fatal" log.txt; master regular expressions and combine them with command line tools, grep It can become a powerful text analysis tool, suitable for log analysis, code retrieval, system debugging and other scenarios. As long as the text pattern can be described, grep can basically find the corresponding content.

grep is one of the most essential tools in Linux for searching text using patterns. Whether you're sifting through logs, configuration files, or code, grep helps you find exactly what you're looking for — fast and efficiently. Here's how to use it effectively for powerful pattern matching.

Basic Syntax and Simple Search

The fundamental structure of grep is:

 grep [options] PATTERN [FILE...]

For example, to find all lines containing "error" in a log file:

 grep "error" /var/log/syslog

This prints every line where the pattern "error" appears (case-sensitive by default).

Tip: If you're unsure about the exact spelling or case, use -i to ignore case:

 grep -i "error" /var/log/syslog

Use Regular Expressions for Advanced Patterns

grep supports regular expressions (regex), which greatly expand your search capabilities.

Common Regex Examples:

• Match start of line with ^ :

   grep "^Failed" /var/log/auth.log

  Finds lines that start with "Failed" — useful for spotting failed login attempts.

• Match end of line with $ :

   grep "ssh$" /var/log/auth.log

  Shows lines ending with "ssh", perhaps indicating specific service messages.

• * Match any character with . and zero or more with ` `**:

   grep "err.*" file.txt

  Matches "error", "err", "errno", etc.

• Match optional character with \? (with extended regex):

   grep -E "colou?r" file.txt

  Finds both "color" and "colour".

Use -E to enable extended regular expressions ( egrep ), so you don't need to escape certain symbols like ? , , | , () .

Useful Options to Enhance Your Search

Here are some practical grep flags that make it far more powerful:

• -r or -R – Recursive search

   grep -r "function myFunction" /home/user/projects/

  Searches all files in the directory (and subdirectories) for the pattern.

• -l – Show only filenames with matches

   grep -rl "TODO" /code/

  Lists files containing "TODO", handy for tracking tasks.

• -n – Show line numbers

   grep -n "password" config.php

  Outputs matching lines along with their line number.

• -v – Invert match (show non-matching lines)

   grep -v "^#" /etc/nginx/nginx.conf

  Filters out comments (lines starting with # ) to see only active config lines.

• -A , -B , -C – Show context

   grep -A 3 -B 2 "error" log.txt

  Displays 3 lines after and 2 lines before each match — great for debugging.

Combine grep with Other Commands

grep shines when used in pipelines. Here are common combinations:

• Filter ps output:

   ps aux | grep nginx

  Shows only processes related to nginx.

• Count occurrences:

   grep -c "warning" system.log

  Returns the number of lines containing "warning".

• Chain multiple patterns:

   grep "fatal" system.log | grep -v "ignored"

  Finds fatal errors but excludes those marked as "ignored".

• Use multiple patterns with -e :

   grep -E "error|fail|fatal" log.txt

  Matches any line containing "error", "fail", or "fatal".

  ---

  grep is simple to start with but incredibly deep. Mastering regex and combining it with other CLI tools turn it into a powerhouse for text analysis. Whether you're debugging, auditing, or exploring data, grep should be in your daily toolkit.

  Basically, if you can describe the text pattern, grep can probably find it.

  The above is the detailed content of How to Use `grep` for Powerful Pattern Matching in Linux. For more information, please follow other related articles on the PHP Chinese website!