File descriptors and redirection in Bash Scripting - Time & Space Complexity

Time Complexity: File descriptors and redirection

O(n)

Understanding Time Complexity

When working with file descriptors and redirection in bash, it is important to understand how the script's execution time changes as it handles more input or output data.

We want to know how the time to run commands grows when redirecting or managing files.

Scenario Under Consideration

Analyze the time complexity of the following bash script snippet.

#!/bin/bash

while read line; do
  echo "$line" >&2
done < input.txt

cat input.txt > output.txt

This script reads each line from input.txt, writes it to standard error, then copies the entire file to output.txt.

Identify Repeating Operations

Look for loops or repeated commands that run multiple times.

• Primary operation: The while read loop reads each line once.
• How many times: It runs once per line in input.txt, so n times if there are n lines.
• Secondary operation: The cat command reads the whole file once to copy it.

How Execution Grows With Input

As the number of lines in input.txt grows, the loop runs more times, and the cat command processes a larger file.

Input Size (n lines)	Approx. Operations
10	~10 loop reads + 1 full file read
100	~100 loop reads + 1 full file read
1000	~1000 loop reads + 1 full file read

Pattern observation: The total work grows roughly in proportion to the number of lines, because each line is read once and the whole file is copied once.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the script grows linearly with the number of lines in the input file.

Common Mistake

[X] Wrong: "Redirection and file descriptor operations happen instantly and do not affect time complexity."

[OK] Correct: Even though redirection looks simple, reading and writing data through file descriptors takes time proportional to the data size, so it affects how long the script runs.

Interview Connect

Understanding how file reading and writing scale helps you write efficient scripts and explain their performance clearly in real situations.

Self-Check

What if we replaced the while read loop with a command that reads the entire file at once? How would the time complexity change?

Practice

1. Which file descriptor number represents the standard error stream in bash?

easy

A. 3

B. 1

C. 2

D. 0

Solution

1. Step 1: Recall standard file descriptors

   Standard input is 0, standard output is 1, and standard error is 2.

2. Step 2: Identify the error stream descriptor

   The error stream is always file descriptor 2 in bash.

3. Final Answer:

   2 -> Option C

4. Quick Check:

   Standard error = 2 [OK]

Hint: Remember: 0=input, 1=output, 2=error [OK]

Common Mistakes:

• Confusing standard output (1) with error (2)
• Thinking input (0) is error
• Using non-standard descriptor numbers

2. Which of the following is the correct syntax to redirect standard output to a file named output.txt in bash?

easy

A. command >> output.txt 2>&1

B. command < output.txt

C. command 2> output.txt

D. command > output.txt

Solution

1. Step 1: Understand output redirection syntax

   Using > redirects standard output (file descriptor 1) to a file, overwriting it.

2. Step 2: Match syntax to redirect output only

   command > output.txt uses > correctly to redirect output to output.txt.

3. Final Answer:

   command > output.txt -> Option D

4. Quick Check:

   Output redirection uses > [OK]

Hint: Use > for output, < for input redirection [OK]

Common Mistakes:

• Using < instead of > for output
• Redirecting error (2>) instead of output
• Appending (>>) when overwrite is needed

3. What will be the output of the following command if file.txt does not exist?

cat file.txt > output.txt 2>&1

medium

A. Redirects both output and error messages to output.txt

B. Creates an empty output.txt file with no error message

C. Outputs the error message to the terminal and creates output.txt

D. Throws a syntax error and does nothing

Solution

1. Step 1: Understand redirection 2>&1

   This redirects standard error (2) to the same place as standard output (1).

2. Step 2: Analyze command behavior when file missing

   cat tries to read file.txt, fails, and sends error to stderr, which is redirected to output.txt along with stdout.

3. Final Answer:

   Redirects both output and error messages to output.txt -> Option A

4. Quick Check:

   2>&1 merges error into output [OK]

Hint: 2>&1 sends errors to the same place as output [OK]

Common Mistakes:

• Thinking error shows on terminal
• Assuming output.txt stays empty
• Confusing 2>&1 with separate redirections

4. Identify the error in this command that attempts to redirect only standard error to error.log:

ls -l > error.log 2>

medium

A. Output redirection > should be 1>

B. Missing filename after 2> for error redirection

C. Should use 2>&1 instead of 2>

D. Command syntax is correct

Solution

1. Step 1: Check error redirection syntax

   Redirection 2> must be followed by a filename to redirect standard error.

2. Step 2: Identify missing filename

   The command ends with 2> but no file is specified, causing a syntax error.

3. Final Answer:

   Missing filename after 2> for error redirection -> Option B

4. Quick Check:

   2> needs a target file [OK]

Hint: Always specify a file after 2> for error redirection [OK]

Common Mistakes:

• Leaving out filename after 2>
• Confusing 2> with 2>&1
• Thinking > needs to be 1>

5. You want to run a script that outputs normal messages to output.log and error messages to error.log. Which command correctly achieves this?

hard

A. ./script.sh > output.log 2> error.log

B. ./script.sh 2>&1 > output.log error.log

C. ./script.sh > output.log 2>&1 error.log

D. ./script.sh > output.log &> error.log

Solution

1. Step 1: Understand separate redirection for output and error

   To send stdout and stderr to different files, use > for stdout and 2> for stderr separately.

2. Step 2: Analyze each option

   ./script.sh > output.log 2> error.log correctly redirects stdout to output.log and stderr to error.log. Others mix or misuse redirection syntax.

3. Final Answer:

   ./script.sh > output.log 2> error.log -> Option A

4. Quick Check:

   Separate > and 2> for output and error [OK]

Hint: Use > for output, 2> for errors to separate files [OK]

Common Mistakes:

• Using &> redirects both to one file
• Mixing order of redirections incorrectly
• Omitting file names after redirection operators