How to Prevent Accidental Deletion in Linux Shell Scripts

Why Shell Scripts Can Accidentally Delete Files

Shell is simple but dangerous; empty variables, spaces, special characters, and failed cd commands can cause rm -rf to delete unintended files.

1. Empty Variables

When a variable expands to an empty string, commands like rm -rf $base_path/$tmp_file may delete the wrong directory.

Solutions:

Use parameter expansion with error checking: echo ${base_path:?var is empty}/${tmp_file:?var is empty} which aborts if a variable is empty.

Manually test for emptiness: [[ ${tmp_file} == "" ]] && echo 1 or [[ -z ${tmp_file} ]] && echo 1.

Enable set -u so that using an unset variable triggers an error. Example script shows the error message.

2. Paths Containing Spaces

Unquoted variables with spaces cause the path to be split, e.g., path="/usr/local /sbin" then # rm -rf $path would delete both parts.

Quote the variable: rm -rf "$path".

3. Special Characters in Filenames

Files or directories named with characters like ~ can be misinterpreted. Example shows # rm -rf ~ deleting the home directory.

Quote the name: rm -rf "~" or preview with echo rm -rf "~" before executing.

4. Failed cd Commands

If cd to a non‑existent directory fails, subsequent rm -rf *.exe runs in the current directory, deleting unintended files.

Use logical short‑circuit: cd path && rm -rf *.exe or verify the directory first: [[ -d ~ ]] && echo 1.

5. Ultimate Safeguards

Avoid performing destructive operations as root whenever possible.

Configure a friendly prompt in login shells to always show the current directory, reducing the chance of operating in the wrong location.