Why Lock files for single instance in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if your script could know when to pause and avoid crashing itself?

The Scenario

Imagine you have a script that runs every hour to update a report. Sometimes, the script takes longer than expected, and the next scheduled run starts before the first one finishes. This causes confusion and errors because both runs try to write to the same files at the same time.

The Problem

Manually checking if a script is already running is tricky and unreliable. You might forget to check, or the check might fail if the script crashes unexpectedly. This leads to overlapping runs, corrupted data, and wasted time fixing problems.

The Solution

Using lock files lets your script create a simple marker when it starts. If the marker exists, the script knows another instance is running and stops itself. This prevents multiple runs from interfering with each other, keeping your data safe and your process smooth.

Before vs After

✗ Before

if pgrep -f myscript.sh; then echo 'Already running'; exit 1; fi
# run script

✓ After

exec 200>/tmp/myscript.lock
flock -n 200 || { echo 'Already running'; exit 1; }
# run script

What It Enables

This lets you safely run scripts on a schedule without worrying about clashes or data corruption.

Real Life Example

A backup script that runs nightly uses a lock file to ensure only one backup runs at a time, preventing disk overload and incomplete backups.

Key Takeaways

Manual checks for running scripts are unreliable and error-prone.

Lock files provide a simple, automatic way to prevent multiple script instances.

This keeps your automation safe, reliable, and easier to manage.

Practice

1. What is the main purpose of using a lock file in a bash script?

easy

A. To prevent multiple instances of the script from running at the same time

B. To speed up the script execution

C. To store user input temporarily

D. To log errors during script execution

Solution

1. Step 1: Understand the role of a lock file

   A lock file is used to signal that a script is already running, preventing duplicates.

2. Step 2: Identify the main purpose

   This prevents multiple script instances from running simultaneously, avoiding conflicts.

3. Final Answer:

   To prevent multiple instances of the script from running at the same time -> Option A

4. Quick Check:

   Lock file purpose = prevent duplicates [OK]

Hint: Lock files stop duplicate script runs quickly [OK]

Common Mistakes:

• Thinking lock files speed up scripts
• Confusing lock files with log files
• Using lock files to store data

2. Which of the following bash commands correctly creates a lock file only if it does not already exist?

easy

A. touch /tmp/myscript.lock

B. echo $$ > /tmp/myscript.lock

C. mkdir /tmp/myscript.lock

D. if [ ! -e /tmp/myscript.lock ]; then touch /tmp/myscript.lock; fi

Solution

1. Step 1: Check for existence before creating

   The command must create the lock file only if it does not exist, so a test with [ ! -e ] is needed.

2. Step 2: Identify the correct syntax

   if [ ! -e /tmp/myscript.lock ]; then touch /tmp/myscript.lock; fi uses an if statement to check and then create the file, which is correct.

3. Final Answer:

   if [ ! -e /tmp/myscript.lock ]; then touch /tmp/myscript.lock; fi -> Option D

4. Quick Check:

   Check existence before touch = if [ ! -e /tmp/myscript.lock ]; then touch /tmp/myscript.lock; fi [OK]

Hint: Use if with [ ! -e ] to create lock file safely [OK]

Common Mistakes:

• Using touch without checking file existence
• Using mkdir which creates a directory, not a file
• Overwriting lock file without check

3. Given this script snippet:

if [ -e /tmp/myscript.lock ]; then
  echo "Script already running"
  exit 1
else
  touch /tmp/myscript.lock
  echo "Running script"
  rm /tmp/myscript.lock
fi

What will be the output if the lock file exists?

medium

A. Running script

B. Script already running

C. No output

D. Error: lock file missing

Solution

1. Step 1: Check the condition when lock file exists

   If /tmp/myscript.lock exists, the if condition is true and the script echoes "Script already running" and exits.

2. Step 2: Understand the output

   Since the script exits early, it does not run or remove the lock file.

3. Final Answer:

   Script already running -> Option B

4. Quick Check:

   Lock file exists = "Script already running" [OK]

Hint: If lock file exists, script exits with message [OK]

Common Mistakes:

• Assuming script runs even if lock file exists
• Expecting no output when lock file exists
• Confusing lock file presence with absence

4. This script is intended to prevent multiple runs using a lock file:

if [ -e /tmp/myscript.lock ]; then
  echo "Already running"
  exit 1
fi

touch /tmp/myscript.lock
# script work here
rm /tmp/myscript.lock

But sometimes multiple instances run simultaneously. What is the likely problem?

medium

A. The lock file is not checked before creation

B. The script does not remove the lock file

C. The lock file is created after the check, causing a race condition

D. The script uses rm instead of rmdir

Solution

1. Step 1: Analyze the timing of lock file creation

   The script checks for the lock file, then creates it. Between these steps, another instance can start and pass the check.

2. Step 2: Identify the race condition

   This gap causes multiple instances to run simultaneously because the lock file is not created atomically with the check.

3. Final Answer:

   The lock file is created after the check, causing a race condition -> Option C

4. Quick Check:

   Race condition from delayed lock creation = The lock file is created after the check, causing a race condition [OK]

Hint: Create lock file atomically to avoid race conditions [OK]

Common Mistakes:

• Ignoring race conditions in lock file creation
• Forgetting to remove lock file after script ends
• Confusing file removal commands

5. You want to write a bash script that runs only one instance at a time using a lock file. Which approach is best to avoid race conditions?

hard

A. Use 'mkdir /tmp/myscript.lock' and check if it succeeds before running

B. Check if lock file exists, then create it with 'touch' if not

C. Create lock file with 'echo $$ > /tmp/myscript.lock' without checking

D. Remove lock file at script start, then create it

Solution

1. Step 1: Understand atomic operations for locking

   Using 'mkdir' to create a directory as a lock is atomic; it either succeeds or fails immediately.

2. Step 2: Compare with other methods

   Other methods like checking then touching can cause race conditions; removing lock at start is unsafe.

3. Final Answer:

   Use 'mkdir /tmp/myscript.lock' and check if it succeeds before running -> Option A

4. Quick Check:

   Atomic mkdir lock = safest method [OK]

Hint: Use mkdir for atomic lock creation to avoid race [OK]

Common Mistakes:

• Using touch without atomic check
• Removing lock file before checking
• Ignoring race conditions