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.