Master the art of shell scripting with advanced patterns, error handling, and automation techniques for Linux systems.

Advanced Bash Scripting Techniques

Bash scripting is a fundamental skill for Linux system administrators. This guide covers advanced techniques for writing robust, maintainable scripts.

Error Handling#

Exit on Error#

#!/bin/bash
set -euo pipefail

# -e: Exit on error
# -u: Exit on undefined variable
# -o pipefail: Exit on pipe failure

Trap for Cleanup#

cleanup() {
    echo "Cleaning up..."
    rm -f /tmp/tempfile
}

trap cleanup EXIT

Advanced Patterns#

Process Substitution#

# Compare two files
diff <(sort file1.txt) <(sort file2.txt)

Parameter Expansion#

# Default values
${VAR:-default}
${VAR:=default}
${VAR:?error message}

Best Practices#

1. Always quote variables
2. Use arrays for multiple values
3. Validate input parameters
4. Implement logging
5. Write unit tests with bats

Example: Robust Backup Script#

#!/bin/bash
set -euo pipefail

BACKUP_DIR="${BACKUP_DIR:-/backups}"
SOURCE_DIR="${1:?Usage: $0 <source_dir>}"

if [[ ! -d "$SOURCE_DIR" ]]; then
    echo "Error: $SOURCE_DIR does not exist" >&2
    exit 1
fi

tar -czf "$BACKUP_DIR/backup-$(date +%Y%m%d).tar.gz" "$SOURCE_DIR"

Conclusion#

Advanced bash scripting techniques enable you to write more robust and maintainable automation scripts.

Production Notes 1#

For Advanced Bash Scripting Techniques, define pre-deploy checks, rollout gates, and rollback triggers before release. Track p95 latency, error rate, and cost per request for at least 24 hours after deployment. If the trend regresses from baseline, revert quickly and document the decision in the runbook.

Keep the operating model simple under pressure: one owner per change, one decision channel, and clear stop conditions. Review alert quality regularly to remove noise and ensure on-call engineers can distinguish urgent failures from routine variance.

Repeatability is the goal. Convert successful interventions into standard operating procedures and version them in the repository so future responders can execute the same flow without ambiguity.

Production Notes 2#

For Advanced Bash Scripting Techniques, define pre-deploy checks, rollout gates, and rollback triggers before release. Track p95 latency, error rate, and cost per request for at least 24 hours after deployment. If the trend regresses from baseline, revert quickly and document the decision in the runbook.

Keep the operating model simple under pressure: one owner per change, one decision channel, and clear stop conditions. Review alert quality regularly to remove noise and ensure on-call engineers can distinguish urgent failures from routine variance.

Repeatability is the goal. Convert successful interventions into standard operating procedures and version them in the repository so future responders can execute the same flow without ambiguity.

Production Notes 3#

For Advanced Bash Scripting Techniques, define pre-deploy checks, rollout gates, and rollback triggers before release. Track p95 latency, error rate, and cost per request for at least 24 hours after deployment. If the trend regresses from baseline, revert quickly and document the decision in the runbook.

Keep the operating model simple under pressure: one owner per change, one decision channel, and clear stop conditions. Review alert quality regularly to remove noise and ensure on-call engineers can distinguish urgent failures from routine variance.

Repeatability is the goal. Convert successful interventions into standard operating procedures and version them in the repository so future responders can execute the same flow without ambiguity.

Production Notes 4#

For Advanced Bash Scripting Techniques, define pre-deploy checks, rollout gates, and rollback triggers before release. Track p95 latency, error rate, and cost per request for at least 24 hours after deployment. If the trend regresses from baseline, revert quickly and document the decision in the runbook.

Keep the operating model simple under pressure: one owner per change, one decision channel, and clear stop conditions. Review alert quality regularly to remove noise and ensure on-call engineers can distinguish urgent failures from routine variance.

Repeatability is the goal. Convert successful interventions into standard operating procedures and version them in the repository so future responders can execute the same flow without ambiguity.