User account management script in Bash Scripting - Time & Space Complexity

Time Complexity: User account management script

O(n)

Understanding Time Complexity

When running a user account management script, it is important to understand how the time it takes grows as the number of users increases.

We want to know how the script's work changes when managing more user accounts.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

users=("alice" "bob" "carol" "dave")

for user in "${users[@]}"; do
  id "$user" >/dev/null 2>&1
  if [ $? -ne 0 ]; then
    useradd "$user"
  fi
  passwd -l "$user"
done

This script checks if each user exists, adds them if not, and then locks their password.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that goes through each user in the list.
• How many times: Once for each user in the users array.

How Execution Grows With Input

As the number of users grows, the script runs the same steps for each user one after another.

Input Size (n)	Approx. Operations
10	About 10 checks and updates
100	About 100 checks and updates
1000	About 1000 checks and updates

Pattern observation: The work grows directly in proportion to the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time taken grows linearly with the number of users to manage.

Common Mistake

[X] Wrong: "The script runs in constant time no matter how many users there are."

[OK] Correct: Because the script does work for each user, more users mean more work and more time.

Interview Connect

Understanding how scripts scale with input size shows you can write efficient automation that handles growing tasks smoothly.

Self-Check

"What if the script also checked each user's group memberships inside the loop? How would the time complexity change?"

Practice

1. What is the main purpose of a bash script that manages user accounts with commands like useradd and userdel?

easy

A. To change the system hostname

B. To automate adding, deleting, and listing users on the system

C. To update software packages automatically

D. To monitor network traffic

Solution

1. Step 1: Understand the commands used

   The commands useradd and userdel are specifically for managing user accounts on Linux systems.

2. Step 2: Identify the script's goal

   Since the script uses these commands, its main purpose is to automate user account management tasks like adding, deleting, and listing users.

3. Final Answer:

   To automate adding, deleting, and listing users on the system -> Option B

4. Quick Check:

   User management commands = automate user tasks [OK]

Hint: Look for user management commands like useradd/userdel [OK]

Common Mistakes:

• Confusing user management with system updates
• Thinking it changes network settings
• Assuming it modifies system hostname

2. Which of the following is the correct syntax to add a new user named alice in a bash script?

easy

A. createuser alice

B. adduser alice

C. newuser alice

D. useradd alice

Solution

1. Step 1: Recall the standard command for adding users

   The standard Linux command to add a user is useradd.

2. Step 2: Match the command with the username

   Using useradd alice correctly adds a user named alice.

3. Final Answer:

   useradd alice -> Option D

4. Quick Check:

   Standard add user command = useradd [OK]

Hint: Remember: useradd is the standard command to add users [OK]

Common Mistakes:

• Using adduser which may not be available on all systems
• Typing createuser or newuser which are invalid commands
• Confusing commands with other system utilities

3. What will be the output of this bash snippet if the script is run with root privileges?

if id "bob" &>/dev/null; then
  echo "User exists"
else
  echo "User does not exist"
fi

medium

A. User does not exist

B. User exists

C. Syntax error

D. Permission denied

Solution

1. Step 1: Understand the id command usage

   The command id "bob" checks if user bob exists. If bob does not exist, it returns an error.

2. Step 2: Analyze the if condition and output

   The script redirects errors to /dev/null, so if bob does not exist, the else branch runs, printing "User does not exist".

3. Final Answer:

   User does not exist -> Option A

4. Quick Check:

   id command fails = else branch runs [OK]

Hint: id command success means user exists; else means no user [OK]

Common Mistakes:

• Assuming output shows error messages
• Thinking permission issues cause output
• Confusing command syntax with errors

4. Identify the error in this script snippet that tries to delete a user named charlie:

userdel charlie
if [ $? -eq 0 ]; then
  echo "User deleted"
else
  echo "Failed to delete user"
fi

medium

A. Missing sudo or root privileges to run userdel

B. Incorrect syntax for if statement

C. userdel command should be userremove

D. No error, script works fine

Solution

1. Step 1: Check command permissions

   The userdel command requires root privileges. Running it without sudo or as root will fail.

2. Step 2: Verify script syntax and commands

   The if statement syntax and command are correct, but permission issues cause failure.

3. Final Answer:

   Missing sudo or root privileges to run userdel -> Option A

4. Quick Check:

   userdel needs root = permission error if missing [OK]

Hint: Remember: userdel needs root or sudo to succeed [OK]

Common Mistakes:

• Thinking userdel syntax is wrong
• Using wrong command name like userremove
• Ignoring permission requirements

5. You want to write a bash script that adds multiple users from a list in a file users.txt. Which script snippet correctly reads each username and adds the user, skipping empty lines?

hard

A. read users.txt | while read user; do
useradd $user
done

B. for user in $(cat users.txt); do
useradd $user
done

C. while read user; do
[ -z "$user" ] && continue
useradd "$user"
done < users.txt

D. cat users.txt | while useradd; do
echo $user
done

Solution

1. Step 1: Understand reading lines safely

   Using while read user reads each line safely, including spaces, and allows skipping empty lines.

2. Step 2: Check skipping empty lines and adding users

   The condition [ -z "$user" ] && continue skips empty lines. Then useradd "$user" adds the user correctly.

3. Final Answer:

   while read user; do [ -z "$user" ] && continue useradd "$user" done < users.txt -> Option C

4. Quick Check:

   Safe line read + skip empty + add user = while read user; do [ -z "$user" ] && continue useradd "$user" done < users.txt [OK]

Hint: Use while read and check empty lines to avoid errors [OK]

Common Mistakes:

• Using for loop with word splitting causing errors
• Incorrect pipe usage with cat and while
• Not skipping empty lines causing useradd errors