grep in scripts in Bash Scripting - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to search for the word 'error' in the file 'log.txt'.

Bash Scripting

grep [1] log.txt

Drag options to blanks, or click blank then click option'

A"error"

B-r

C-v

D-i

Attempts:

3 left

💡 Hint

Common Mistakes

Using an option like -i without the pattern.

Forgetting to put the search word in quotes.

The correct syntax to search for the word 'error' is to provide it as a quoted string argument to grep.

2fill in blank

medium

Complete the code to search for the word 'fail' in 'report.txt' ignoring case.

Bash Scripting

grep [1] "fail" report.txt

Drag options to blanks, or click blank then click option'

A-r

B-v

C-i

D-c

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-v' which inverts the match.

Using '-c' which counts matches instead of showing them.

The '-i' option makes grep ignore case when searching.

3fill in blank

hard

Fix the error in the script to count lines containing 'warning' in 'system.log'.

Bash Scripting

count=$(grep [1] system.log | wc -l)
echo $count

Drag options to blanks, or click blank then click option'

A"-c"

B"-i"

C"-v"

D"warning"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-c' as a pattern instead of an option.

Putting options inside quotes as pattern.

The pattern 'warning' should be given as a string to grep. Using '-c' as a pattern is incorrect here.

4fill in blank

hard

Fill both blanks to create a script that searches recursively for 'TODO' in the current directory and shows line numbers.

Bash Scripting

grep [1] [2] "TODO" .

Drag options to blanks, or click blank then click option'

A-r

B-n

C-i

D-v

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-v' which inverts the match.

Using '-i' which ignores case but is not required here.

The '-r' option searches recursively, and '-n' shows line numbers in the output.

5fill in blank

hard

Fill all three blanks to create a script that searches for lines NOT containing 'debug' in 'app.log' and counts them.

Bash Scripting

grep [1] [2] "debug" app.log | wc [3]

Drag options to blanks, or click blank then click option'

A-v

B-i

C-l

D-c

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-c' which counts bytes instead of lines.

Forgetting to invert the match with '-v'.

The '-v' option inverts the match to exclude 'debug'. '-i' ignores case. '-c' counts the matching lines with wc.

Practice

1. What does the grep command do in a bash script?

easy

A. Searches for lines matching a pattern in files or input

B. Deletes files matching a pattern

C. Creates new files with matching names

D. Changes file permissions based on a pattern

Solution

1. Step 1: Understand grep's purpose

   The grep command is used to search text for lines that match a given pattern.

2. Step 2: Compare options

   Options B, C, and D describe actions unrelated to searching text, so they are incorrect.

3. Final Answer:

   Searches for lines matching a pattern in files or input -> Option A

4. Quick Check:

   grep = search text lines [OK]

Hint: grep finds text patterns in files or input quickly [OK]

Common Mistakes:

• Thinking grep deletes or modifies files
• Confusing grep with commands like rm or chmod
• Assuming grep creates files

2. Which of the following is the correct syntax to search for the word "error" in a file named log.txt using grep?

easy

A. grep -f error log.txt

B. grep error log.txt

C. grep log.txt error

D. grep -c log.txt error

Solution

1. Step 1: Identify grep syntax

   The correct syntax is grep [pattern] [file]. So, searching for "error" in "log.txt" is grep error log.txt.

2. Step 2: Check other options

   grep -f error log.txt uses -f which expects a file of patterns, not a pattern string. Options C and D have arguments reversed or wrong flags.

3. Final Answer:

   grep error log.txt -> Option B

4. Quick Check:

   grep pattern file = correct syntax [OK]

Hint: Remember: grep pattern filename [OK]

Common Mistakes:

• Swapping pattern and filename order
• Using -f flag incorrectly
• Confusing -c flag usage

3. What will be the output of this script snippet?

echo -e "apple\nbanana\nApple" | grep -i apple

medium

A. apple

B. No output

C. apple\nApple

D. Apple

Solution

1. Step 1: Understand the input

   The input lines are "apple", "banana", and "Apple".

2. Step 2: Apply grep with -i option

   The -i option makes grep case-insensitive, so it matches both "apple" and "Apple" but not "banana".

3. Final Answer:

   apple\nApple -> Option C

4. Quick Check:

   grep -i matches case-insensitive lines [OK]

Hint: Use -i to ignore case when searching [OK]

Common Mistakes:

• Ignoring case sensitivity of grep
• Expecting only lowercase matches
• Assuming grep outputs only one match

4. Identify the error in this script snippet:

if grep "error" logfile.txt
then
  echo "Error found"
fi

medium

A. Missing semicolon or newline before then

B. grep command syntax is wrong

C. echo command should be outside if block

D. fi is missing

Solution

1. Step 1: Check if statement syntax

   In bash, the if condition must end with a semicolon or newline before then. Here, then is on a new line and the previous line ends properly, so syntax is correct.

2. Step 2: Confirm other parts

   grep syntax is correct, echo is correctly inside if, and fi is present.

3. Final Answer:

   No error in the script snippet -> Option A

4. Quick Check:

   if condition syntax is correct as given [OK]

Hint: Put ; or newline before then in if statements [OK]

Common Mistakes:

• Writing if and then on same line without semicolon
• Misplacing fi or echo commands
• Confusing grep syntax with if syntax

5. You want to count how many lines in data.txt contain the word "success" ignoring case, and store the number in a variable count. Which script snippet correctly does this?

hard

A. count=$(grep -i success -c data.txt)

B. count=$(grep -c success -i data.txt)

C. count=$(grep success -i -c data.txt)

D. count=$(grep -ci success data.txt)

Solution

1. Step 1: Understand grep options

   The -c option counts matching lines, and -i ignores case. Both can be combined as -ci.

2. Step 2: Check option order and syntax

   Options A, B, and D have options separated or misplaced. count=$(grep -ci success data.txt) correctly combines -c and -i before the pattern and filename.

3. Final Answer:

   count=$(grep -ci success data.txt) -> Option D

4. Quick Check:

   Use combined options -ci for count and ignore case [OK]

Hint: Combine options like -ci for count and ignore case [OK]

Common Mistakes:

• Separating options incorrectly
• Placing options after filename
• Not combining -c and -i properly