Page 2 - Bash

A script with #!/bin/sh runs fine on your own machine and fails on a Debian server with a cryptic error. The reason is the gap between Dash and Bash: two shells with a shared POSIX base but very different feature sets.

A nightly mysqldump usually lands unchecked in the backup directory until it's needed in an emergency and turns out to be empty or outdated. An automated database dump analysis in Bash reads size trends, table row counts, and schema changes directly from the dump file, without restoring it into a test database.

PATH hijacking exploits the fact that Bash scripts resolve commands through an inherited, potentially manipulated PATH variable instead of using fixed, trusted paths. This article shows how a manipulated PATH or IFS tricks a script into running someone else's programs, why cron jobs and systemd units are especially affected, and which concrete measures harden Bash scripts against this attack pattern.

Comparing two CSV exports, finding out what got added, what is missing and what is shared: sort, uniq and comm solve this task without a database and without an external scripting language, simply through the right combination of three classic Unix tools.

Classic wait blocks until every started background job is done, which caps parallelism at the boundaries of whole batches. wait -n instead waits for the first job to finish, whichever one it is, finally making worker pools with consistently high utilization practical, without reaching for external tools like GNU Parallel.

A deployment script without checklists deploys even when the build is broken. Without guards, a second deployment runs in parallel with the first. Without a rollback mechanism, a failed deployment turns into a manual emergency. Professional shell scripts for deployments solve all three problems, using simple, maintainable Bash patterns.

A script using mapfile or sed -i runs fine on the Linux server and breaks on a colleague's MacBook. The reason is the outdated Bash 3.2 that ships with macOS and the different coreutils Apple provides for licensing reasons.

A config generator replaces hand maintained copies of .env files and server configurations with a single template per format, combined with clearly separated variables per environment. This article shows how to build such a config generator with envsubst, strict secrets separation, and a validation stage in Bash, so development, staging, and production never drift apart again.

Grouping a log file with a hundred thousand lines by status code, calculating totals per customer, or building a formatted report from raw CSV: awk does all of that without Python, without a database, right inside the pipe. Fields, associative arrays and BEGIN/END blocks turn it into a full featured reporting tool.

Many shell scripts fail silently: a command returns exit code 1, the pipeline keeps going, and monitoring sees nothing. set -euo pipefail, ERR traps with LINENO, and clean exit codes are the foundation of every Bash script that needs to run reliably in production and react instantly and traceably when something goes wrong.